-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Remove the pip3.x entrypoint from the pip wheel #12536
Conversation
The pip3.x entrypoint in the pip wheel was misleading, because the pip wheel works for any python 3 version. Pip continues to special-case itself to generate that version specific entry point when it installs itself.
Thanks for the ping, i'll adjust uv! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is setup.py
still needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can remove it. I wanted to do it in another PR in case anyone has comments about that: #12537.
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.
Having a pip3.x entrypoint in the py3-none-any pip wheel is incorrect.
Pip continues to special-case itself to generate that version specific entry point when it installs itself, so having it in the wheel is useless and arguably a remnant of
setup.py install
times.Related: #3164, #8010, pypa/packaging.python.org#1505
I can imagine relatively
far fetchedniche workflows that could be disturbed by this change, but I tend to think correctness should prevail.