Live data from Hacker News

Numpy: Plan for dropping Python 2.7 support

github.com

21–30 of 390 posts

Re: Numpy: Plan for dropping Python 2.7 support

#22
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.

Twisted port is a work in progress.

Re: Numpy: Plan for dropping Python 2.7 support

#23
post #20
post #17

Earlier quoted context omitted.

> 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...

Those are internal tools at best so it won't matter that much for migration.

Re: Numpy: Plan for dropping Python 2.7 support

#24
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.

Twisted port is a work in progress.

Ah, forgot about twisted. The new asyncio stuff probably changes a lot for how something like that could be implemented.

Re: Numpy: Plan for dropping Python 2.7 support

#26
I cheered Python's slow and steady 2.7 -> 3 move when it began but I'll admit I started to have some doubts a couple of years ago when it still had not completed. In hindsight I think it has been exceptionally well managed and is likely to keep Python in good stead for many years to come.

Re: Numpy: Plan for dropping Python 2.7 support

#27
post #8

Earlier quoted context omitted.

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 onlooke…

That's a very melodramatic comment for someone who clearly hasn't been keeping track of the 3.x changelogs – which pretty much all contain at least one compelling update to the language. Modern Python is v3. Legacy support drop-off is the same with any project.

Re: Numpy: Plan for dropping Python 2.7 support

#29
post #18
post #9

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

Define 'supported'? Many banks are still writing COBOL.

By that logic any language can be supported by never upgrading the system. Support implies some kind of active support from the creators / maintainers of the language, not active use by people.
Post reply on HN