Draft: Add python 3.13 compatibility #2536
Open
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
Author
|
Contributor
|
@gregunz Now 3.9 has been dropped, are you interested in reviving this PR? |
Author
|
@Fokko: Sure, I can take the time this week to review it! |
This was referenced Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Rationale for this change
Updated Ray to 2.45 to allow compatibility with python 3.13
Added filter for new sqlite3 “unclosed database” warnings in Python 3.13.
New Python 3.13 warnings see here : Added a filter to silence unclosed database warnings from sqlite3 introduced in Python 3.13. A comprehensive solution could be changing the code to get rid of these.
Are these changes tested?
Ran tests locally with 3.13.
Are there any user-facing changes?
Yes, ray version change required on Python 3.13.