-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ensurepip: add configure --with-wheel-pkg-dir=PATH to get wheel packages from a system directory #87022
Comments
The Fedora packaging policy recommends to "unbundle" bundled dependencies. "Fedora packages SHOULD make every effort to avoid having multiple, separate, upstream projects bundled together in a single package." The main motivation is to ease updates when fix serious vulnerabilities (less packaging work). The ensurepip package contains bundled wheel packages of setuptools and pip: $ ls Lib/ensurepip/_bundled/
pip-20.2.3-py2.py3-none-any.whl
setuptools-47.1.0-py3-none-any.whl The Fedora python3 package doesn't contain the ensurepip._bundled package: $ python3
Python 3.9.1 (default, Dec 8 2020, 00:00:00)
>>> import ensurepip._bundled
ModuleNotFoundError: No module named 'ensurepip._bundled' Instead, a separated RPM package python-pip-wheel provides wheel packages in /usr/share/python-wheels/ directory: $ ls /usr/share/python-wheels/
pip-20.2.2-py2.py3-none-any.whl*
setuptools-49.1.3-py3-none-any.whl*
wheel-0.34.2-py2.py3-none-any.whl* Fedora has a downstream patch on ensurepip (written by Miro Hrončok) to always use /usr/share/python-wheels/: https://src.fedoraproject.org/rpms/python3.10/blob/master/f/00189-use-rpm-wheels.patch Fedora has packages of 9 CPython versions: 2.6, 2.7, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.10. https://developer.fedoraproject.org/tech/languages/python/multiple-pythons.html Having a separated package for wheel packages allows us to upgrade a single package (python-pip-wheel) for setuptools/pip bugfix or security vulnerability. -- I propose to add a new --with-wheel-pkg-dir=PATH option to the ./configure script. If used, ensurepip will only use wheel packages from this directory. Otherwise, the existing code is unchanged. In short, the behavior is unchanged, unless the option is used explicitly. If a directory is specified but wheel packages are missing, ensurepip fails. If the directory contains multiple wheel packages of different versions, the most recent version is used of each package. Note: In practice, the Fedora package only provides a single wheel package of each Python module. But I propose to make the Python upstream code as generic as possible. I'm working on a pull request to implement this. Downstream Fedora issue: https://bugzilla.redhat.com/show_bug.cgi?id=1874803 -- Fedora (Miro) already contributed to ensurepip to make ensurepip less dependent on pip internals: commit 88f82b2
This change was already related to Fedora downstream change to get wheel packages from a different directory. Fedora can use a different pip version (older or more recent) than ensurepip._bundled. |
An alternative is to find packages in all directories and pick the most recent version. Example with a specified directory *and* ensurepip._bundled is available:
Most recent versions:
Problem: I'm not sure that pip is fully compatible with any setuptools version. |
For simplicity, I would avoid mixing wheels from 2 different directories. |
Right. I wrote PR 24210 which is simpler. It either uses bundled wheels, or wheels from the directory. |
We (SUSE) have updated versions of the wheels as special Sources, and then this in the %prep stage of our SPEC file:
A bit of manual work required, but it doesn't lead to so incredible convoluted constructs as I see in Fedora (nothing against it, but our build system is already convoluted enough). |
In Fedora, we update the wheels independently without rebuilding Python. What incredible convoluted constructs do you have in mind in particular? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: