Closed timf34 closed 2 years ago
Hiya, unfortunately this is part of the SB3/Gym/SS/PZ incompatibility soup. We are actively working on bringing everything up to speed, and much of the focus so far has been placed on reducing the technical debt in Gym. For now, the workaround is to try upgrading SS to the latest version (3.5.0) and seeing if that error still persists. Would you mind reporting back if it does?
Hi,
Yep so what I am now doing is running it on WSL2. I found another issue where you thankfully commented your setup which I have now copied, and is working despite warnings regarding conflicts:)
I am running Windows 10 otherwise, and am not sure why but it would not work on that, but with WSL2 it passes.
I might also add ray[rllib]
into that incompatibility soup, as that also depends on an old version of gym and is what the codebase I am working on is built out of. But yeah 13_lines.py
passes when using WSL and the setup you guys posted in the comment above.
Thanks for your work!
Tim
Just to be clear, it works on WSL, not on Windows, even when I upgrade to supersuit==3.5.0
That's interesting, Windows is not officially supported by these few libraries (in large part because the developers behind them are predominantly Linux/OSX users).
However, if you're able to figure out how to get it to work on Windows, we'd happily work with you on a PR to get it implemented.
Sounds good!
Getting it working on Windows is not a priority for me at the moment and am just going to continue ahead with WSL for now - but I might come back to it to work on that in a while! Thanks
Ok, no problem. Is it safe for me to close this issue?
Sounds good:)
Hi,
When I run the below sample code from the
README.md
file, I get the following error:NotImplementedError: Calling seed externally is deprecated; call reset(seed=seed) instead
This is the code sample that I run:
I am using this with
supersuit==3.3.3
andpettingzoo==1.8.1
I should also note that I am using
gym==0.21.0
(this is the latest version stable-baselines3 is compatible with)I should also note that there is a similar issue here however that was inactive and had been closed without being resolved.
Thanks
Here is the full traceback: