Repository navigation
Add Python 3.13 to list of allowed Python versions - #11411
Merged
Merged
Conversation
zanieb
approved these changes
May 13, 2024
dhruvmanila
approved these changes
May 13, 2024
charliermarsh
force-pushed
the
charlie/py313
branch
from
May 13, 2024 16:29
307a66c to
356500d
Compare
charliermarsh
enabled auto-merge (squash)
May 13, 2024 16:29
Contributor
|
Member
|
I guess one other thing we could do is update UP035 to emit a diagnostic if |
Member
Author
|
Makes sense, mind filing an issue (or PRing it)? :) |
Member
|
Closed
1 task done
This branch was previously deployed
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
4 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
I believe we're already "Python 3.13-ready"? The main Ruff-impacting change I see in https://docs.python.org/3.13/whatsnew/3.13.html is PEP 696 which Jelle added in #11120.