add 3.16 to embedded wheel versions#3140
Merged
Merged
Conversation
Contributor
Author
|
without this alternatively -- and perhaps a better change -- I think the |
Contributor
Author
|
my chatters pointed out that this potentially was a mistake in 04af502#diff-a532364d3821049224ee1eacaf7664a3488002bc40fe7d68f849a000c4dc257bR40 |
Contributor
Let's fix that now. |
this makes it more likely to be successful when a new python version is released
gaborbernat
approved these changes
May 11, 2026
This was referenced May 12, 2026
gaborbernat
added a commit
that referenced
this pull request
May 12, 2026
The daily `Upgrade embedded dependencies` workflow keeps regenerating `src/virtualenv/seed/wheels/embed/__init__.py` with `MAX = "3.8"` and dropping the `3.16` entry β both of which had to be hand-patched in #3140 on top of the auto-PR. The script is the source of the regression, so patching the generated file alone leaves the next cron run free to undo the fix again. π The `MAX` substitution in `render_init` was reading the first key of the ordered support table, which is always the lowest Python version, so it baked `MAX = '3.8'` into the rendered module on every regen. Emit the runtime expression `next(reversed(BUNDLE_SUPPORT))` as literal text in the template instead, so the rendered module evaluates it at import time and always points at the highest supported version regardless of what the table contains. The `SUPPORT` range stopped at `3.15`, which is why each regen also dropped the `3.16` entry. Extend the range through `3.16` so the generated table covers the versions we already ship wheels for. No runtime behavior changes for users β this only affects what the regen task writes, so no changelog fragment is needed.
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
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.
No description provided.