add support for Python 3.15#1454
Open
AlexWaygood wants to merge 1 commit into
Open
Conversation
meta-cla
Bot
added
the
CLA Signed
thatch
approved these changes
Jun 23, 2026
thatch
left a comment
thatch
left a comment
Contributor
There was a problem hiding this comment.
Looks good (I came up with similar changes independently).
|
This would be a good time to go ahead and bump PyO3 to 0.29, which fixes RUSTSEC-2026-0176 and RUSTSEC-2026-0177. |
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
3 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.
Summary
Add support for running and building LibCST on Python 3.15 and 3.15t.
PyO3 0.28 is needed to build the native extension on 3.15, and requires bumping the minimum Rust version to 1.83. This also updates uv and cibuildwheel for the new prerelease interpreters.
Finally, refresh coverage.py: the previously locked version crashes while tracing tests on 3.15.
Following the precedent set in [#1203, #1331 and #1345, this is a CI-focussed change that does not add support for parsing new Python 3.15 syntax. That would need to be done separately.
Fixes #1445.
Test plan
I ran all tests that I could locally; CI should hopefully confirm whether this looks in good shape!