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
Building Python3.11.0 with ensurepip incorrectly includes bin/pip3.10 #98682
Comments
Hmm, actually, a correction -- my main branch was behind. At tag |
Looking at the contents of [console_scripts]
pip = pip._internal.cli.main:main
pip3 = pip._internal.cli.main:main
pip3.10 = pip._internal.cli.main:main |
Looks like a pip bug. pip contains logic to specially fix |
Fix submitted to pypa/pip#11547 |
Gentle suggestion: Although the problem's roots are in I just verified locally that removing the unzip Lib/ensurepip/_bundled/pip-22.3-py3-none-any.whl pip-22.3.dist-info/entry_points.txt
sed -i '/pip3\.10/d' pip-22.3.dist-info/entry_points.txt
zip Lib/ensurepip/_bundled/pip-22.3-py3-none-any.whl pip-22.3.dist-info/entry_points.txt |
It’s plausible. The |
It seems this problem also affects the Windows install binaries. I installed
|
Is this still an issue? We've updated pip at least a couple of times since early 2023. |
Repeating for [console_scripts]
pip = pip._internal.cli.main:main
pip3 = pip._internal.cli.main:main
pip3.11 = pip._internal.cli.main:main
Is this a problem? |
pip automatically excludes pipX and pipX.Y entry points when it installs itself, so the pip3.11 line should not affect things in practice. The original bug was due to pip having faulty logic for ignoring the entry points. This has been fixed on pip’s side, and the up-to-date versions bundled in CPython branches do not contain the bug now. |
Sounds fixed then. If it repros, we can look again. |
Bug report
Building Python3.11.0 with
--ensure-pip
seems to incorrectly createpip3.10
in addition topip3
andpip3.11
, wherepip3.10
is identical topip3.11
.Building Python3.11 at v3.11.0:
Observing the problem:
Your environment
Building on linux-x86_64.
The text was updated successfully, but these errors were encountered: