Announcement: pip 20.1b1 beta release
On behalf of the PyPA, I am pleased to announce that a beta release of pip, pip 20.1b1, has been released. I hope you will help us by testing this and checking for new bugs in how pip deals with complicated projects and dependencies. The highlights for this release are: * Significant speedups when building local directories, by changing behavior to perform in-place builds, instead of copying to temporary directories. * Significant speedups in `pip list --outdated`, by parallelizing network access. This is the first instance of parallel code within pip's codebase. * A new `pip cache` command, which makes it possible to introspect and manage pip's cache directory. * Better `pip freeze` for packages installed from direct URLs, enabled by the implementation of PEP 610. We would be grateful for all the testing that users could do to ensure that, when pip 20.1 is released, it's as solid as we can make it. You can upgrade to this beta with `python -m pip install -U --pre pip`. This release also contains an alpha version of pip's next generation resolver. It is **off by default** because it is **unstable and not ready for everyday use**. If you're curious about this, please visit this GitHub issue about the resolver, what doesn't work yet, and what kind of testing would help us out https://github.com/pypa/pip/issues/8099 . The full changelog is available. https://pip.pypa.io/en/latest/news/ As with all pip releases, a significant amount of the work was contributed by pip's user community. Huge thanks to all who have contributed, whether through code, documentation, issue reports and/or discussion. Your help keeps pip improving, and is hugely appreciated. Specific thanks go to Mozilla (through its Mozilla Open Source Support Awards) and to the Chan Zuckerberg Initiative DAF, an advised fund of Silicon Valley Community Foundation, for their support that enabled the work on the new resolver. -- Sumana Harihareswara pip project manager under contract with Python Software Foundation Changeset Consulting https://changeset.nyc
On 23. 04. 20 21:36, Sumana Harihareswara wrote:
We would be grateful for all the testing that users could do to ensure that, when pip 20.1 is released, it's as solid as we can make it.
We are doing some basic testing in Fedora. So far everyhting looks good. We've tested: Basic CI smoke testing with venvs, virtualenvs, tox: - CPython 3.5-3.8 (will add 3.9) - PyPy 3.6 Bundling in Fedora and running non-network tests during build on CPython 3.8.2 and 3.9.0a5. Building couple PEP 517/518 packages (pytest, pluggy, clickit, entyrpoints). Building and self-testing CPython 3.5-3.9 and PyPy 3.6 using a wheel of this pip, passed their ensurepip and venv tests during the build. I have now experienced some weird permissions: /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/INSTALLER 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/RECORD 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/direct_url.json 600 Will try to reproduce this outside of our build environment and will report an issue. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
On Mon, 27 Apr 2020 at 16:21, Miro Hrončok <mhroncok@redhat.com> wrote:
On 23. 04. 20 21:36, Sumana Harihareswara wrote:
We would be grateful for all the testing that users could do to ensure that, when pip 20.1 is released, it's as solid as we can make it.
We are doing some basic testing in Fedora.
So far everyhting looks good.
We've tested:
Basic CI smoke testing with venvs, virtualenvs, tox: - CPython 3.5-3.8 (will add 3.9) - PyPy 3.6
Bundling in Fedora and running non-network tests during build on CPython 3.8.2 and 3.9.0a5.
Building couple PEP 517/518 packages (pytest, pluggy, clickit, entyrpoints).
Building and self-testing CPython 3.5-3.9 and PyPy 3.6 using a wheel of this pip, passed their ensurepip and venv tests during the build.
I have now experienced some weird permissions:
/usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/INSTALLER 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/RECORD 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/direct_url.json 600
Will try to reproduce this outside of our build environment and will report an issue.
I suspect this is https://github.com/pypa/pip/issues/8139 (for which we have a fix prepared). Paul
On 27. 04. 20 17:31, Paul Moore wrote:
On Mon, 27 Apr 2020 at 16:21, Miro Hrončok <mhroncok@redhat.com> wrote:
On 23. 04. 20 21:36, Sumana Harihareswara wrote:
We would be grateful for all the testing that users could do to ensure that, when pip 20.1 is released, it's as solid as we can make it.
We are doing some basic testing in Fedora.
So far everyhting looks good.
We've tested:
Basic CI smoke testing with venvs, virtualenvs, tox: - CPython 3.5-3.8 (will add 3.9) - PyPy 3.6
Bundling in Fedora and running non-network tests during build on CPython 3.8.2 and 3.9.0a5.
Building couple PEP 517/518 packages (pytest, pluggy, clickit, entyrpoints).
Building and self-testing CPython 3.5-3.9 and PyPy 3.6 using a wheel of this pip, passed their ensurepip and venv tests during the build.
I have now experienced some weird permissions:
/usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/INSTALLER 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/RECORD 600 /usr/lib/python3.8/site-packages/pip-20.1b1.dist-info/direct_url.json 600
Will try to reproduce this outside of our build environment and will report an issue.
I suspect this is https://github.com/pypa/pip/issues/8139 (for which we have a fix prepared).
Yes indeed. I have opened https://github.com/pypa/pip/issues/8153 in the meantime (the linked issue didn't rally stand out when searching). Closed as duplicate. This would indeed generate a lot of problems in Fedora if not fixed in 20.1. Thanks! -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
Thanks for the testing, all. Pip 20.1 is now out and https://pip.pypa.io/en/latest/news/ has the changes since the beta. -- Sumana Harihareswara Changeset Consulting https://changeset.nyc
On 27. 04. 20 17:17, Miro Hrončok wrote:
Basic CI smoke testing with venvs, virtualenvs, tox: - CPython 3.5-3.8 (will add 3.9)
CPython 3.9.0a5 venv, virtualenv, tox OK as well. I've also observed that we now have the direct_url.json when we build pip, that leaks the builddir path: {"archive_info": {}, "url": "file:///builddir/build/BUILD/pip-20.1b1/dist/pip-20.1b1-py2.py3-none-any.whl"} I will read PEP 610, but may I safely assume that we can just rm it to have the previous behavior? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
On 27. 04. 20 20:56, Miro Hrončok wrote:
I've also observed that we now have the direct_url.json when we build pip, that leaks the builddir path:
{"archive_info": {}, "url": "file:///builddir/build/BUILD/pip-20.1b1/dist/pip-20.1b1-py2.py3-none-any.whl"}
I will read PEP 610, but may I safely assume that we can just rm it to have the previous behavior?
Followup in https://discuss.python.org/t/4012 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok
participants (3)
-
Miro Hrončok -
Paul Moore -
Sumana Harihareswara