I'm happy to announce the release of pip 6.0 and virtualenv 12.0.
A High level overview of what this brings:
* PEP 440 is fully implemented now and pip will use specifiers and the version selection logic as specified there.
* HTTP access will now be cached by default in pip, speeding up repeated downloads of the same file automatically.
* Randomized and secure build directories are used by default in most situations.
* Accessing an insecure origin (Invalid HTTPS or HTTP) by default is now deprecated. For HTTP this will continue to work in pip 6.0 but raise a warning and for HTTPS this will not work. You may use --trusted-host example.com to re-enable this on a per-host basis.
* Added per-virtualenv and a machine global configuration file, as well as support platform standard directories for configuration.
* Support environment markers inside of a requirements file.
* Support environment markers inside of a setuptools extra.
* Automatically retry failed HTTP requests.
* Greatly reduce the verbosity of the pip command by default.
* Updated virtualenv to have setuptools 8.2.1 and pip 6.0 bundled.
* Many many bugfixes and smaller changes.
As always please file any issues with either https://github.com/pypa/pip/issues or https://github.com/pypa/virtualenv/issues.
--- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
On Tue, Dec 23, 2014 at 12:44 AM, Tshepang Lekhonkhobe tshepang@gmail.com wrote:
Why the jump from 1.5.6 to 6.0?
The release notes say (under "6.0"):
"PROCESS Version numbers are now simply X.Y where the leading 1 has been dropped."
(from https://pip.pypa.io/en/latest/news.html )
I'm guessing this is to start honoring the convention (e.g. from semver) that backwards incompatible changes should only be made when the major version number is incremented.
--Chris
Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
On Dec 23, 2014, at 3:55 AM, Chris Jerdonek chris.jerdonek@gmail.com wrote:
On Tue, Dec 23, 2014 at 12:44 AM, Tshepang Lekhonkhobe tshepang@gmail.com wrote:
Why the jump from 1.5.6 to 6.0?
The release notes say (under "6.0"):
"PROCESS Version numbers are now simply X.Y where the leading 1 has been dropped."
(from https://pip.pypa.io/en/latest/news.html )
I'm guessing this is to start honoring the convention (e.g. from semver) that backwards incompatible changes should only be made when the major version number is incremented.
--Chris
Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
It’s a mixture of things.
* We don’t generally have massive breaking releases, we tend to deprecate things over time and remove them a few versions later. This means that each 1.X+1 broke something that worked in 1.X.
* There was an allure to do a big "2.0" style breakage that this completely negates.
* Given the first item, what to do for the version after 1.9 was a question, we could just do 1.10 but given we didn't want to do a big 2.0 style breakage and we didn't have any plans to increment the 1, we'd likely just keep doing 1.X+1 for a very long time.
--- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
-
Chris Jerdonek -
Donald Stufft -
Tshepang Lekhonkhobe