Use pip from specified python cmd - #2115
Merged
Merged
Conversation
twangboy
approved these changes
Jun 26, 2026
twangboy
requested changes
Jul 9, 2026
twangboy
force-pushed
the
use-same-pip-as-python
branch
from
August 31, 2026 19:35
46bbbe4 to
87cf647
Compare
twangboy
enabled auto-merge (rebase)
September 2, 2026 17:33
twangboy
approved these changes
Sep 2, 2026
…llback
Check the exit status of '$_pip_cmd --version' directly instead of
relying on captured-output emptiness, silence stderr so a missing
pip module doesn't dump a traceback, and re-capture _pip_version
after the pip${_py_version} fallback succeeds so it isn't reported
empty even though a working pip binary was found.
twangboy
force-pushed
the
use-same-pip-as-python
branch
from
September 2, 2026 17:34
87cf647 to
0ae25f3
Compare
twangboy
disabled auto-merge
September 2, 2026 17:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Tries to use a
pipthat's matched to the specifiedpythoncmd, either:<python_cmd> -m pip(egpython3.14 -m pip)pip<py_version>(egpip3.14)What issues does this PR fix or reference?
When a version of python is specified (eg with
-x python3.14arg to the bootstrap script), but a correspondingpipcommand isn't available, the old behavior was to try using a pip of the major version (egpip3), but this is problematic if that version of pip does exist, but doesn't match the python version used to build packages. That results in: