[PR #12641/1aef5d70 backport][3.13] Make pip command configurable via PIP variable in Makefile#12644
Merged
bdraco merged 2 commits intoMay 19, 2026
Conversation
(cherry picked from commit 1aef5d7)
bdraco
commented
May 19, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 3.13 #12644 +/- ##
==========================================
- Coverage 98.29% 98.29% -0.01%
==========================================
Files 128 128
Lines 44881 44881
Branches 2440 2440
==========================================
- Hits 44117 44116 -1
Misses 589 589
- Partials 175 176 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
5 tasks
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
1 participant
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.
This is a backport of PR #12641 as merged into master (1aef5d7).
What do these changes do?
Adds a
PIP ?= python -m pipvariable to the Makefile and threads$(PIP)through every install recipe (.update-pip,.install-cython,.install-deps,.develop,install); downstream CI such as yarl can now runmake .develop PIP="uv pip"to install via uv without us maintaining a parallel.develop-uvtarget.Are there changes in behavior for the user?
No; the default expands to the existing
python -m pipinvocation, so contributors and existing CI see no difference.Is it a substantial burden for the maintainers to support this?
No; it is one variable plus five mechanical substitutions, and the default value preserves current behavior.
Related issue number
Follow-up to aio-libs/yarl#1716, which switched yarl's downstream aiohttp test runner to uv but still falls back to pip inside
make .develop.Checklist
CONTRIBUTORS.txtCHANGES/folderCHANGES/12641.contrib.rst.Drafted with Claude Code (claude-opus-4-7); reviewed by @bdraco.