Move numpy to >= 2.0 (numpy 1.* goes end of life in september)#124
Open
pablovela5620 wants to merge 1 commit intofacebookresearch:mainfrom
Open
Move numpy to >= 2.0 (numpy 1.* goes end of life in september)#124pablovela5620 wants to merge 1 commit intofacebookresearch:mainfrom
pablovela5620 wants to merge 1 commit intofacebookresearch:mainfrom
Conversation
numpy 1.* reaches eol come september 2025, migrate over to numpy>= 2.0
facebook-github-bot
added
the
CLA Signed
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
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.
numpy 1.* reaches eol come september 2025, migrate over to numpy>= 2.0
I tested this out and had no issues when running with cuda 12.8 and pytorch==2.7.0
Let me know if there's a specific reason for staying below 2.0