Add compatibility with numpy 2.0 #1094
Merged
Conversation
This file contains 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
RedTachyon
changed the title
1 task
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.
Numpy broke some things with the 2.0 release: https://numpy.org/doc/stable/release/2.0.0-notes.html
The tentative policy is that Gymnasium will support both numpy 1.x and 2.x, at least for the foreseeable future. Of course there will be complications everywhere in downstream projects that have other dependencies, but the changes are minor enough that we should be able to handle it here. There will also be minor incompatibilities here, like conflicts with pytorch, and the fact that numpy 2.0 doesn't support python 3.8. Nothing we can do about that.