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

11–20 of 115 posts

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

#11

Post by geofft »

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

Because it's the stable branch, and it gets no major version updates for anything after release, nor any new packages, just bugfixes to the current version.

There is backports, and I've thought about maintaining a newer Python interpreter in backports (when I was working for a company using Jessie and trying to use a Debian stack for everything and sort of wanting async syntax). You could introduce python3.6 or python3.7 as a new package in backports. But it would be extremely hard to update the Python modules in Debian to the newer version, too, because there's just a "python3-foo" package for each module, so you'd either have to recompile all binary modules and patch them to work on the newer Python as necessary (and patch anything using async or await as regular identifiers....), or you'd have to introduce an interpreter that intentionally wasn't compatible with modules installed as Debian packages. (Or you could introduce an interpreter that tried its best and failed randomly, which seems worse than either option.) I'm personally sympathetic to wanting to get /usr/bin/python3.6 from my OS even if the only useful thing to do is put a virtualenv on top, but I think it makes sense to just install Python yourself into /usr/local at that point.

Re latexmk, it looks like the volunteer maintainer hasn't updated it since 2015, and there's a culture of not stepping on people's toes and waiting a while before assuming they're inactive or no longer care. But it's been updated in the development release. The current changelog https://metadata.ftp-master.debian.org/changelogs/main/l/lat... has a bunch of "NMU" entries, non-maintainer uploads.

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

#12

Post by backprojection »

mrosett wrote: post #8
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.

The code I've written recently relies heavily on async and data classes, both of which are recent additions. I can't imagine choosing Python 2 at this point.

Same here. Dataclasses and type annotations are fantastic, not to mention f-strings.

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

#13

Post by mehrdadn »

geofft wrote: post #11
mehrdadn wrote: post #7

Earlier quoted context omitted.

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

Because it's the stable branch, and it gets no major version updates for anything after release, nor any new packages, just bugfixes to the current version. There is backports, and I've thought about maintaining a newer Python interpreter in backports (when I was working for a company using Jessie and trying to use a Debian stack for everything and sort of wanting async syntax). You could introduce python3.6 or pytho…

Thanks for the explanation.

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

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

#14

Post by geofft »

mehrdadn wrote: post #13
geofft wrote: post #11

Earlier quoted context omitted.

Because it's the stable branch, and it gets no major version updates for anything after release, nor any new packages, just bugfixes to the current version. There is backports, and I've thought about maintaining a newer Python interpreter in backports (when I was working for a company using Jessie and trying to use a Debian stack for everything and sort of wanting async syntax). You could introduce python3.6 or pytho…

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

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

#15

Post by emddudley »

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.

> the stock Python 3 shipped for CentOS 7.

What package are you referring to? As I understand it there is no "stock" Python 3 in CentOS 7. There is just what you can get from secondary repos, like EPEL, SCL, and IUS. Those repos now have 3.6 available.

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

#16

Post by mehrdadn »

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

..Oh. Wow. Do distros not care if their packages are updated for 3+ years? I'd have expected half their entire job is to make sure package maintainers are actually maintaining packages...

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

#19

Post by kalefranz »

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.

I generally try to leave the system python alone. Use pyenv or conda to get the python interpreters for your own code and apps.

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

#20

Post by Svenstaro »

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

Just to note: in Arch we almost only have individual package maintainers.
Post reply on HN