Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think the sunsetting is very premature. Python 3 became a stable and viable alternative only since 3.6.1 (look at the evolution of async/await before that for example). Giving it 2 years is definitely not enough for enterprise (unless their focus is startup, tinkerers and data scientists)


I mean, arguably they’ve been telling you too move for far longer. So it seems reasonable to sunset it after 10 years.


So migrate a large production codebase to unstable API? With dependencies not yet migrated?


Loads of open source and commercial projects have already made the switch to python 3 years ago. If all of them could do it, so could your org. No excuses, you've made your bed, etc.


Much of the work could have been done ahead of time.


That being said - python 3 was released in 2008. A 12 year transition is pretty respectable.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: