Skip to content
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

[Bug Report] Error after updating to MiniGrid 1.2.0 #232

Closed
ibagur opened this issue Sep 10, 2022 · 1 comment · Fixed by #233
Closed

[Bug Report] Error after updating to MiniGrid 1.2.0 #232

ibagur opened this issue Sep 10, 2022 · 1 comment · Fixed by #233

Comments

@ibagur
Copy link

ibagur commented Sep 10, 2022

Describe the bug
I have upgraded to MiniGrid 1.2 (after updating to gym 0.26), but for some reason I cannot get it run. I have forked and cloned the repository so to download the code, but haven't performed any changes to it yet.

Code example

I try to run just the manual control script over a simple environment:

./gym_minigrid/manual_control.py --env MiniGrid-Empty-5x5-v0

I get the following errors:

Traceback (most recent call last):
File "./gym_minigrid/manual_control.py", line 102, in
env = gym.make(
File "/Users/inigo/.local/share/virtualenvs/test-minigrid-ZLPD9hGZ/lib/python3.8/site-packages/gym/envs/registration.py", line 652, in make
raise e
File "/Users/inigo/.local/share/virtualenvs/test-minigrid-ZLPD9hGZ/lib/python3.8/site-packages/gym/envs/registration.py", line 640, in make
env = env_creator(
_kwargs)
File "/Users/inigo/Documents/cursos/Data Science/master_viu/work/test-minigrid/gym-minigrid/gym_minigrid/envs/empty.py", line 72, in init
super().init(
TypeError: init() got an unexpected keyword argument 'new_step_api'

System Info

  • Describe how gym-minigrid was installed (pip, docker, source, ...)
  • Forked the repo into my github, cloned it locally and just installed following the instructions:

git clone https://github.com/ibagur/gym-minigrid.git
cd gym-minigrid
pip3 install -e .

  • What OS/version of Linux you're using: MacOS 11.6
  • Python version : 3.8.6

Additional context

It seems something related to 'new_step_api' argument, but I cannot relate it to other issues that made reference to it

Checklist

  • [ X] I have checked that there is no similar issue in the repo (required)
@rodrigodelazcano rodrigodelazcano mentioned this issue Sep 10, 2022
10 tasks
@rodrigodelazcano
Copy link
Member

Sorry about this @ibagur and thank you for notifying the bug. This PR #233 should fix this issue. The fix will be included in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants