mark mujoco-py environments as explicity deprecated
#926
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
pseudo-rnd-thoughts
approved these changes
Feb 16, 2024
|
It would make sense to move to Gymnasium-robotics I believe, @Kallinteris-Andreas how do you feel about that? |
|
depends on how compatible it is with |
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.
Description
This PR simply changes the documentation to explicitly state that
mujoco-pyare deprecatedsince this issue, it is clear that the inclusion of the old MuJoCo environments causes issues to user who do not interact with it
I am not sure about when, the removal of
mujoco-pyenvironments will happen, probably after 1.0, maybe with the release ofpy313?Fixes # (issue)
Type of change