Repository navigation
docs: make 3.15 the newest Python in the standard - #138
Merged
Merged
Conversation
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.
Summary
Every repo now tests CPython 3.15, and 3.15t where it tests free-threading. PV1 names the newest stable minor and its free-threaded build, so its example moves from
3.14/3.14tto3.15/3.15t. The standard asks for the exemptions table to change in the same pull request, so the three rows that name a free-threaded build move with it.Changes
3.15and3.15t.modern-di-arqandmodern-di-grpcexemptions: they are exempt from PV1's free-threaded entry, which is now3.15t. Their reasons are unchanged. grpcio 1.84.0, the newest release, still ships no free-threaded wheel; I did not recheckhiredis.lite-bootstrapexemption: its smoke job runs on3.14tand3.15t. The row said3.13tand3.14t, but the job had no3.13tentry.CI6's example (
compose2poddrops3.14tfor PyYAML) is unchanged. It is still true;compose2podnow drops3.15fromfloorsfor the same reason.Checklist
uv run pytestpasses (175 tests)uv run mkdocs build --strictpasses