Re:Pip 10 has been released
by piinbinary on Saturday April 14, 2018 @12:44PM
(#16838114)
Presumably it still supports Python 2.7, so this isn't actually the end of Python 2 support.
[ Parent
| on HN ]
Re:Pip 10 has been released
by ognyankulev on Saturday April 14, 2018 @01:06PM
(#16838217)
Python 2.6 was 2% of pip downloads and apparently this was the rationale for dropping its support: https://github.com/pypa/pip/pull/4343 . This led to some Python libraries to also drop 2.6, as shown by library commits referencing this pull request.
RHEL/CentOS 6 stock python is 2.6, IIRC.
RHEL/CentOS has a reputation of keeping up zombie software that is long unsupported by upstream. It's their model and their problem, rest of community shouldn't IMHO care. Hardly any projects have resources to keep compatibility with their ten-years-old releases and backport every fix.
I doubt anybody running it is interested in upgrading their pip.
You would be surprised at the requests I get from people running CentOS 6.
Is there any reason those people can't leave their system python to the system, and otherwise bring their own?
They don’t know how.
But anaconda python will work nicely on centos 6 I suspect.
Quite nice. And likely faster and more secure. Do an independent check for yourself. Look at the compile flags. Along with what’s statically linked, vs what conda manages as dynamically linked. Also don’t miss what all the pip-installed wheels are statically linking.
Correct. https://pypi.python.org/pypi/pip/10.0.0 lists "Programming Language :: Python :: 2.7".
2.6 was released on 01-Oct-2008 and the last security-fix release was on October 29, 2013.
Humorously, https://www.python.org/download/releases/2.6/ says "Python 2.6 has been replaced by a newer bugfix release of Python. Please download Python 2.6.7 instead."
Following the link to 2.6.7 says "Python 2.6.7 has been replaced by a newer security-fix only source release of Python. Please download Python 2.6.8 instead."
Following the link to 2.6.8 says "Please download Python 2.6.9 instead." Which finally took me to the final release of the 2.6 series.
The reason it links you to 2.6.6 instead of 2.6.9 is because 2.6.6 is the newest version that has binaries available for download. You have to compile the newer versions from source if you want to use them.
It never linked me to 2.6.6. It went to 2.6.7.
2.6.6 isn't mentioned at https://www.python.org/download/releases/2.6/ nor in my earlier comment.