-
Notifications
You must be signed in to change notification settings - Fork 856
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
Special case pip entrypoint names #1593
Comments
Thanks for the report! No idea why this would be. |
Isn't that |
@henryiii , Yes, corrected. |
My guess is that it's a caching issue. We cache interpreter metadata using the ctime, to avoid having to run the Python interpreter on every invocation (which is expensive, in a relative sense). Perhaps the ctime isn't changing here? |
Err wait, sorry -- so it creates a file named |
There is no version info in the pip-entrypoint.
|
pip has an entrypoint pip3.10 in its wheel: https://files.pythonhosted.org/packages/8a/6a/19e9fe04fca059ccf770861c7d5721ab4c2aebc539889e97c7977528a53b/pip-24.0-py3-none-any.whl. I think you're supposed to special case pip entrypoints (pypa/pip#11547)? |
The pip discord pointed me to https://github.com/pypa/pip/blob/3898741e29b7279e7bffe044ecfbe20f6a438b1e/src/pip/_internal/operations/install/wheel.py#L283, we should special case pip. |
@konstin - Do you mind taking this one? |
Users expect pip to have `pip`, `pip3` and `pip3.x` entrypoints. But pip is a universal wheel, so it contains the `pip3.x` entrypoint where it was built on. To fix this, pip special cases itself when installing (https://github.com/pypa/pip/blob/3898741e29b7279e7bffe044ecfbe20f6a438b1e/src/pip/_internal/operations/install/wheel.py#L283), replacing the wheel entrypoint with one for the current version. We now do the same. Fixes #1593
Users expect pip to have `pip`, `pip3` and `pip3.x` entrypoints. But pip is a universal wheel, so it contains the `pip3.x` entrypoint where it was built on. To fix this, pip special cases itself when installing (https://github.com/pypa/pip/blob/3898741e29b7279e7bffe044ecfbe20f6a438b1e/src/pip/_internal/operations/install/wheel.py#L283), replacing the wheel entrypoint with one for the current version. We now do the same. Fixes #1593
Reopening because the upstream fix breaks my workaround: pypa/pip#12536 |
Update #1918 to handle pypa/pip#12536, where pip removed their python minor entrypoints. Closes #1593.
Update #1918 to handle pypa/pip#12536, where pip removed their python minor entrypoints. Closes #1593.
Update #1918 to handle pypa/pip#12536, where pip removed their python minor entrypoints. Closes #1593.
Update #1918 to handle pypa/pip#12536, where pip removed their python minor entrypoint. The pip test is semi-functional since it builds pip from source instead of using a wheel with the wrong entrypoint, we have to update it when this pip version has a release. Closes #1593.
on Alma Linux 9.2, using uv 0.1.3
python3.x all installed via pyenv
the pip / pip3 / pip3.10 are all identical and correct,
so it's just an incorrect filename.
all other versions also create a pip3.10:
The text was updated successfully, but these errors were encountered: