Conversation
Contributor
Author
|
Seems like NumPy 1.26.4 is not ready for python 3.13 just for Windows. I guess we wait. IO tests passed though which is nice! |
Contributor
Author
|
Actually there is no guarantee that 3.13 will work with 1.26 so let me drop that soon. Seems like there's no point to updating to 3.13 until we have the numpy 2.0 stuff solved |
Contributor
Author
|
Will be closed by #1490 :) |
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
1 participant
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.
Python 3.13 released. See notes here. We should be testing for it now :)
I think we had mentioned we wanted our CI to be oldest and newest python at some point too. Let's see what happens...