Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NumPy 1.16 is the last release to support Python 2.7

github.com

Post reply on HN
Print view View original

41–50 of 115 posts

Re: NumPy 1.16 is the last release to support Python 2.7

#41

Post by dralley »

mr_toad wrote: post #29
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

2009. Seriously, it’s been 10 years since Python 3 came out, Python 2.x has been supporting legacy code since then.

Python 3.3 was the first version >3 that was actually "good". Prior versions were, if not unusable, not a great experience. Even when writing new code. And some of the Python core devs (Raymond Hettinger) share that opinion.

And let's not understate what a big deal it was to break compatibility like that. Porting a sufficiently complex project is non-trivial.

Re: NumPy 1.16 is the last release to support Python 2.7

#42

Post by [deleted] »

mehrdadn wrote: post #7
gammateam wrote: post #5

Earlier quoted context omitted.

Debian also does not have anything above python 3.4 on the stable packages branch 3.6 has been dev and test since 2016

Why in the world is Debian like this? Their buggy latexmk is also from 2015. Somehow I feel like every system that I want to keep updated stays on an old version, and every system that I want to keep pinned to some version just force-feeds me its updates...

[deleted]

Re: NumPy 1.16 is the last release to support Python 2.7

#43

Post by [deleted] »

ac130kz wrote: post #33
gnulinux wrote: post #28

Earlier quoted context omitted.

EDIT: My comment is grossly misunderstood and I cannot delete my comment. I did not imply python 3 causes bad code, I was trying to tell a story about how "our" python 2 code is handsome and python 3 code is ugly; sorta implying python2 is not necessarily legacy code. I have absolutely no problem with python 3 and prefer it over python 2. I do not want to start a 2 vs 3 flamewar please just ignore this comment. === M…

Python3 was cleaned up pretty well, however it's up to devs whether to use the latest cryptic features no one understands.

[deleted]

Re: NumPy 1.16 is the last release to support Python 2.7

#44

Post by xtreak29 »

blattimwind wrote: post #9
lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

3.4 will reach EOL very soon.

> The expectation is that Python 3.4.10 will be released in March of 2019, and this will be the final release of Python 3.4.

https://www.python.org/dev/peps/pep-0429/#release-schedule

Re: NumPy 1.16 is the last release to support Python 2.7

#46

Post by beagle3 »

lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

If you need the new numpy, get a new python. Conda makes that painless, but whichever way you get numpy, python itself is easier to build/install.

Re: NumPy 1.16 is the last release to support Python 2.7

#47

Post by explainplease »

geofft wrote: post #14
mehrdadn wrote: post #13

Earlier quoted context omitted.

Thanks for the explanation. Re latexmk: so am I getting the development release on Arch? I get the 2018 version with texlive-core.

Sorry, I mean that the volunteer maintainer of the latexmk package in Debian hasn't updated it since 2015. Arch probably has a newer version from the latexmk authors (and I think Arch does not have the same culture of individual package maintainers, in general).

The Debian LaTeX maintainer was essentially harassed out of the project by the Anti-Harassment Team.

Re: NumPy 1.16 is the last release to support Python 2.7

#48

Post by SlowRobotAhead »

mr_toad wrote: post #29
anonymousCar wrote: post #17

When can we start calling Python 2.7 legacy code?

2009. Seriously, it’s been 10 years since Python 3 came out, Python 2.x has been supporting legacy code since then.

Biggest failure of the Python group is definitely the 2.7 / 3.x nonsense. It annoys me greatly when I see new code on 2.7, thanks a lot Nordic.

Re: NumPy 1.16 is the last release to support Python 2.7

#49

Post by nurettin »

lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

async stuff is a bit suspicious to me. I use an async web server to command an async websocket client and sometimes you get hard to debug problems like throwing an exception in one library causing the other to stop working. That's never happened to me in node.

Re: NumPy 1.16 is the last release to support Python 2.7

#50

Post by coldtea »

lykr0n wrote: post #4

Just rip the band-aid off. Some of the async stuff in Python 3 is awesome. A bit curious that 3.4 has been dropped, as that's the stock Python 3 shipped for CentOS 7.

>Just rip the band-aid off. Some of the async stuff in Python 3 is awesome.

Will that awesome async stuff help us migrate several 100s of thousands of lines of 2.7 code?

Post reply on HN