-
Notifications
You must be signed in to change notification settings - Fork 516
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
[Enhancement] Deprecate --gym-packages argument #390
Comments
Interesting... I didn't know about that undocumented feature. Yes, makes sense then (and we need to double check but the yaml/python config file should work too with this). The other thing we need to double check is the name convention for the envs. |
To explain in some more detail how it works: if you do If this module registers some environments upon being imported, then those environments are then in scope and are created with the usual FWIW the feature is documented in Gymnasium, but maybe not as exposed as it should be |
yes, that's what After a quick check, rl-baselines3-zoo/rl_zoo3/exp_manager.py Lines 608 to 612 in 660f2d3
|
We will also have another problem: rl-baselines3-zoo/rl_zoo3/train.py Lines 161 to 171 in 660f2d3
EDIT: we can skip that check when |
BTW: environment name normalization for gym_ids with this prefix should be fixed soonish: huggingface/huggingface_sb3#32 |
🚀 Feature
Deprecate or even remove the
--gym-packages
argument.Motivation
Since
gym
0.21.0 you can pass<package>:<gym_id>
togym.make()
to make it automatically import the given package. This turns the--gym-packages
flag into duplicate functionality that unnecessarily clutters the interface.Pitch
Remove the argument and add a hint about the feature in the documentation.
Alternatives
No response
Additional context
I learned about this feature by @RedTachyon here
Checklist
The text was updated successfully, but these errors were encountered: