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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release numpy <2 pin, and support python 3.13 #719
release numpy <2 pin, and support python 3.13 #719
Changes from 4 commits
5a2f2dc
3753d5e
a264fb8
c1639c0
d7a6d02
7c39f8f
0a3b012
82f6dd1
89c03fe
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I decide to drop this pin entirely because I believe it's something
torch
should resolve instead ofmonty
(i.e.torch
should correctly list supportednumpy
)Unless
tensor.numpy()
should not be used at certain versions? I'm not atorch
user, input appreciated!Plan B (which I don't really like because it would narrow the default supported NumPy version) is to have something like: