Sunsetting Python 2

Re:Sunsetting Python 2 by dangxiaopin on Monday September 09, 2019 @11:18AM (#20918957)

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)

[ Parent | on HN ]

Re:Sunsetting Python 2 by AlphaSite on Monday September 09, 2019 @11:26AM (#20919029)

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

[ Parent | on HN ]

Re:Sunsetting Python 2 by dangxiaopin on Monday September 09, 2019 @11:31AM (#20919072)

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

[ Parent | on HN ]

Re:Sunsetting Python 2 by partialrecall on Monday September 09, 2019 @11:54AM (#20919301)

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.

[ Parent | on HN ]

Re:Sunsetting Python 2 by mixmastamyk on Monday September 09, 2019 @12:14PM (#20919484)

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

[ Parent | on HN ]

Re:Sunsetting Python 2 by pudquick on Monday September 09, 2019 @11:25AM (#20919018)

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

[ Parent | on HN ]