The only thing keeping me on Python 2.7 is Apache Beam, but it's becoming increasingly painful and I'm close to just using a different technology rather than deal with making all my code py2 compatible in 2019...
NumPy 1.16 is the last release to support Python 2.7
21–30 of 115 posts
Re: NumPy 1.16 is the last release to support Python 2.7
#22Earlier 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
It's not very clear, but this release is last release supporting 2.7 & 3.4. 1.5.6 supports 3.4.
I don't understand your comment. Version 1.5.6 of what?
The NumPy 1.16.0 notes say
> Support for Python 3.4 been dropped, the supported Python versions are 2.7 and 3.5-3.7.
That definitely sounds like NumPy 1.16.0 doesn't support python 3.4.
Re: NumPy 1.16 is the last release to support Python 2.7
#23Earlier quoted context omitted.
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...
I don't know who these "distros" people are. Humans care. But no humans cared-enough to update this earlier. If you want to contribute to the Debian project specifically, talk to me.
Re: NumPy 1.16 is the last release to support Python 2.7
#24Earlier quoted context omitted.
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...
Eventually such packages get removed (usually when they stop building for whatever reason). But if the package still works, having an old version of it is still better than not having anything.
Re: NumPy 1.16 is the last release to support Python 2.7
#25The only thing keeping me on Python 2.7 is Apache Beam, but it's becoming increasingly painful and I'm close to just using a different technology rather than deal with making all my code py2 compatible in 2019...
For those interested, you can track Beam Python 3 support progress here:
Re: NumPy 1.16 is the last release to support Python 2.7
#26When can we start calling Python 2.7 legacy code?
Now.
seriously. I think we have to treat it as legacy code now.
Re: NumPy 1.16 is the last release to support Python 2.7
#27Just 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.
This. I don't use anything but Anaconda these days. I leave the system Python alone.
Re: NumPy 1.16 is the last release to support Python 2.7
#28When can we start calling Python 2.7 legacy code?
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.
===
My company has >1 million line of python 2.7. About 1.5 year ago we managed to pass our test harness (about 80% line coverage) in python 3. At the moment we can't do that but we believe if we tried hard for a few weeks we can do it again too. I don't know how we define "legacy code" but I code in this codebase everyday and the code is actually very pretty and understandable. We also have a python 3 project (only a few thousand line of code) and god that code is definitely ugly as shit. Even after python2 goes unmaintained, I will still think our python3 code looks more like legacy.
Re: NumPy 1.16 is the last release to support Python 2.7
#29When 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.
Re: NumPy 1.16 is the last release to support Python 2.7
#30When can we start calling Python 2.7 legacy code?
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…
If your Python 2 code is clean and your Python 3 is ugly, I don't know what the hell you are doing. They are almost the same language. Are you trolling?