Enable Python 3.13 support, allow numpy 2.x #568
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
Codecov Report✅ All modified and coverable lines are covered by tests. |
Collaborator
Author
|
The tests pass, so I think we can make this change. Feel free to merge if you agree, @stefanradev93. |
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.
TensorFlow has released a Python 3.13 compatible version, which was blocking us the last time we wanted to enable Python 3.13 support. Also, I have read the NumPy 2.0 migration guide, and there was nothing that stood out to me that would require action. With the test coverage we have now, I hope anything that could cause problems will show up in the tests.
I have adapted the test to run version 3.13, I will undo this when the tests have successfully passed.