-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Open
Labels
type: maintenanceRelated to Development and Maintenance ProcessesRelated to Development and Maintenance Processes
Description
What's the problem this feature will solve?
Currently for regular PRs pip only tests against the oldest supported Python version and the newest supported Python version:
Lines 175 to 182 in ec5faea
- "3.8" | |
# Commented out, since Windows tests are expensively slow, | |
# only test the oldest and newest Python supported by pip | |
# - "3.9" | |
# - "3.10" | |
# - "3.11" | |
# - "3.12" | |
- "3.13" |
But when pip does a final release I think it would be reassuring for all versions of Python to be tested against.
Describe the solution you'd like
Somehow in the GitHub workflow file have a condition that runs all untested versions of Python for the final release.
Alternative Solutions
Do nothing.
Additional context
I don't know how to implement this yet, but if no one else does this I plan to spend a bit of time investigating this in the future and raise a PR. I'm guessing have a job associated with a specific path filter on NEWS.rst
that tests these versions of Python on Windows.
Code of Conduct
- I agree to follow the PSF Code of Conduct.
Metadata
Metadata
Assignees
Labels
type: maintenanceRelated to Development and Maintenance ProcessesRelated to Development and Maintenance Processes