-
Notifications
You must be signed in to change notification settings - Fork 335
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
[Feature Request] Support for Gymnasium #613
Comments
Thanks for this @pseudo-rnd-thoughts ## Some context: Many of our users stick to a specific gym version (e.g. habitat or robotic people) and they're happy with it. As a SOTA library we obviously want to support latest changes too! VersioningI see that gymnasium starts at 0.26.3, meaning that it's one step ahead of gym. So I guess we'd be good with the code snippet you provided above (since we'll be calling I guess we can take care of that. I'll keep you posted on the progress. |
Thanks for the quick response. That works for us Do you mind me asking why 0.13 is the minimum? Edit: A migration guide to v26 and we have a legacy compatibility wrapper from v21 to v26 wrappers in gym / gymnasium v26 https://gymnasium.farama.org/content/migration-guide/ |
For what it's worth, if you want to keep old API compatibility and a more supported older version of Gym, we'd recommend using 0.21. Upgrading from 0.13 to 0.21 shouldn't even be especially difficult |
Mainly hardware requirements. |
Motivation
Gymnasium is a fork of the OpenAI Gym project by that same people that maintained Gym for the last 18 months.
Our understanding from OpenAI is that they are not planning on maintaining Gym currently therefore, we would recommend using Gymnasium.
For more information about this, see our announcement - https://farama.org/Announcing-The-Farama-Foundation
Solution
Currently, the Gymnasium and Gym are identical repos so should be compatible between the two projects.
However in the future, we are planning on adding a new feature improvements that this repo would be interested in
The text was updated successfully, but these errors were encountered: