Live data from Hacker News

Numpy: Plan for dropping Python 2.7 support

github.com

11–20 of 390 posts

Re: Numpy: Plan for dropping Python 2.7 support

#12
post #9

It would be interesting to see whether Python 2 is the longest supported major version for a programming language.

Python 2 came out in 2000 and goes EOL 2020 I think. Perl 5 was released in 1994 and has no planned EOL date, so it is currently winning by a fair margin.

Re: Numpy: Plan for dropping Python 2.7 support

#14
post #9

It would be interesting to see whether Python 2 is the longest supported major version for a programming language.

What? No! Python 2 is only 17 years old.

I can still run Java, C, C++ and Perl 5 (picking the first 4 languages that occur) that were written before then, with no problems.

Re: Numpy: Plan for dropping Python 2.7 support

#16
post #10

Good. The glacial migration from Python 2 to 3 is one of the worst things about an otherwise fantastic ecosystem. The tide is turning though, with Django having already dropped support for 2, and now with Numpy too hopefully Python 2 can be properly consigned to the history books. For people wondering why it's been like this for almost a decade(!) since Python 3.0 was released: Python 3.0 was actually terrible. It la…

Yeah, for the longest time everyone kept using library support as an excuse for sticking with 2. But at this point I think it's the exception that a decent Python library doesn't support 3, rather than the rule.

The only one that comes to mind for me is fabric, to be honest.

Re: Numpy: Plan for dropping Python 2.7 support

#17
post #16
post #10

Good. The glacial migration from Python 2 to 3 is one of the worst things about an otherwise fantastic ecosystem. The tide is turning though, with Django having already dropped support for 2, and now with Numpy too hopefully Python 2 can be properly consigned to the history books. For people wondering why it's been like this for almost a decade(!) since Python 3.0 was released: Python 3.0 was actually terrible. It la…

Yeah, for the longest time everyone kept using library support as an excuse for sticking with 2. But at this point I think it's the exception that a decent Python library doesn't support 3, rather than the rule. The only one that comes to mind for me is fabric, to be honest.

> But at this point I think it's the exception that a decent Python library doesn't support 3, rather than the rule.

Right now 187 of the top 200 packages on Pypi support Python 3. https://python3wos.appspot.com/

Re: Numpy: Plan for dropping Python 2.7 support

#19
post #8

At the SciPy 2017 conference, for the first time I saw speakers who were presenting new libraries say that they were not going to be developing Python2 versions. Quite a change from a year or two ago.

All my libraries have been py3-only since around last year. I'm also not caring much about supporting 2 on the old ones I maintain. 2 is pretty old, it's time to move on.

> 2 is pretty old, it's time to move on.

Why? Just because "it's pretty old?" The 2-to-3 change seems mostly cosmetic. When Python users ignored 3, Python devs started flogging their dead horse. When the horse still refused to move, disappointed riders started shouting "shame!" at users who suggested that the horse looked dead. Eventually, the riders tied ropes to the horse and pulled it along the ground. The onlookers either switched to bicycles and cars, or figured that they might as well ride the man-hauled carcass awhile longer.

Re: Numpy: Plan for dropping Python 2.7 support

#20
post #17
post #16

Earlier quoted context omitted.

Yeah, for the longest time everyone kept using library support as an excuse for sticking with 2. But at this point I think it's the exception that a decent Python library doesn't support 3, rather than the rule. The only one that comes to mind for me is fabric, to be honest.

> But at this point I think it's the exception that a decent Python library doesn't support 3, rather than the rule. Right now 187 of the top 200 packages on Pypi support Python 3. https://python3wos.appspot.com/

And of the 13 not migrated, 9 are Mozilla packages, so they're probably just waiting to write them all in Rust...
Post reply on HN