Sunsetting Python 2

Re:Sunsetting Python 2 by kortilla on Monday September 09, 2019 @10:16AM (#20918378)

Strings in python3 were terrible for memory well into mid-3. Raymond Hettinger is a core dev and he recently stated on Twitter that he didn’t feel py3 was a clear upgrade win until this most current release.

[ Parent | on HN ]

Re:Sunsetting Python 2 by zurtex on Monday September 09, 2019 @11:02AM (#20918820)

Raymond has been consistent in saying Python 3.6.1 was the release where Python 3 became better than Python 2. That was March 21, 2017, and we're now in Python 3.7.4.

I appreciate the general point that that's far more recent than Python 3s initial release but it's also a large exaggeration to say "until this most current release".

Also to understand why it took so long is because Python 2 kept improving after Python 3s release. Python 2.7 was a great release and many further features from Python 3 got backported in it's 2.7.x point release.

[ Parent | on HN ]

Re:Sunsetting Python 2 by kortilla on Monday September 09, 2019 @09:44PM (#20924413)

Sorry, I misremembered. 3.8 is the first one he said is a clear winner: https://twitter.com/raymondh/status/1167218640095043586

[ Parent | on HN ]

Re:Sunsetting Python 2 by loeg on Tuesday September 10, 2019 @03:43AM (#20925932)

2017 is a lot more recent than 2008 (Py 3.0).

[ Parent | on HN ]