Fwd: [pypi-announce] upgrade to pip 20.2 -- plus changes coming in 20.3
A new pip is out. Please see below, upgrade, and let us know if devpi users start to have trouble. In particular, we need your feedback on the beta of the new dependency resolver, because we want to make it the default in the October release. We have a low-traffic, announce-only list to announce major changes to pip/PyPI -- subscribe at https://mail.python.org/mailman3/lists/pypi-announce.python.org/ . best, Sumana Harihareswara, pip project manager -------- Forwarded Message -------- Subject: [pypi-announce] upgrade to pip 20.2 -- plus changes coming in 20.3 Date: Thu, 30 Jul 2020 11:24:58 -0400 From: Sumana Harihareswara <sh@changeset.nyc> Reply-To: distutils-sig@python.org Organization: Changeset Consulting To: pypi-announce@python.org On behalf of the Python Packaging Authority, I am pleased to announce the release of pip 20.2. Please upgrade for speed improvements, bug fixes, and better logging. You can install it by running python -m pip install --upgrade pip. We make major releases each quarter, so this is the first new release since 20.1 in April. NOTICE: This release includes the beta of the next-generation dependency resolver. It is significantly stricter and more consistent when it receives incompatible instructions, and reduces support for certain kinds of constraints files, so some workarounds and workflows may break. Please test it with the `--use-feature=2020-resolver` flag. Please see our guide on how to test and migrate, and how to report issues <https://pip.pypa.io/en/latest/user_guide/#changes-to-the-pip-dependency-reso...>. The new dependency resolver is *off by default* because it is *not yet ready for everyday use*. For release highlights and thank-yous, please see <https://blog.python.org/2020/07/upgrade-pip-20-2-changes-20-3.html> . The full changelog is at <https://pip.pypa.io/en/stable/news/>. Future: We plan to make pip's next quarterly release, 20.3, in October 2020. We are preparing to change the default dependency resolution behavior and make the new resolver the default in pip 20.3. -- Sumana Harihareswara project manager for pip, on contract with Python Software Foundation Changeset Consulting, https://changeset.nyc _______________________________________________ pypi-announce mailing list -- pypi-announce@python.org To unsubscribe send an email to pypi-announce-leave@python.org https://mail.python.org/mailman3/lists/pypi-announce.python.org/ -- Sumana Harihareswara Changeset Consulting https://changeset.nyc
On 30 Jul 2020, at 22:15, Sumana Harihareswara wrote:
Thanks for the heads up. I saw the announcement. Is there anything in particular that makes you think there could be issues with devpi? A quick scan of the changelog didn't bring anything up from my side. The dependency resolver is fully on the pip side with no involvement of devpi. Regards, Florian Schulze
On Fri, Jul 31, 2020, at 2:19 AM, Florian Schulze wrote:
Great question. I should have said -- please try it out, and please ask devpi users to try it out and report problems. There is nothing in particular about the interaction of devpi and the new resolver that makes me expect problems. However, I figure that devpi *users* might have particular quirks in the packages they're making/sharing/installing (ones that are not available on PyPI), and that those quirks might lead to problems with the new resolver. And they need to know about the coming changes in what pip allows in constraints files. I'd like for those users to find out about dependency snarls and requirements glitches now, not in October, so we all have a chance to fix stuff (on their side and ours). Thanks, Sumana
On 30 Jul 2020, at 22:15, Sumana Harihareswara wrote:
Thanks for the heads up. I saw the announcement. Is there anything in particular that makes you think there could be issues with devpi? A quick scan of the changelog didn't bring anything up from my side. The dependency resolver is fully on the pip side with no involvement of devpi. Regards, Florian Schulze
On Fri, Jul 31, 2020, at 2:19 AM, Florian Schulze wrote:
Great question. I should have said -- please try it out, and please ask devpi users to try it out and report problems. There is nothing in particular about the interaction of devpi and the new resolver that makes me expect problems. However, I figure that devpi *users* might have particular quirks in the packages they're making/sharing/installing (ones that are not available on PyPI), and that those quirks might lead to problems with the new resolver. And they need to know about the coming changes in what pip allows in constraints files. I'd like for those users to find out about dependency snarls and requirements glitches now, not in October, so we all have a chance to fix stuff (on their side and ours). Thanks, Sumana
participants (2)
-
Florian Schulze -
Sumana Harihareswara