Skip to content

Moving to gymnasium compatibility #32

@marimeireles

Description

@marimeireles

I'm creating this issue to discuss my current ideas/progress on making whynot compatible with the latest version of gymnasium.

I'm thinking about erasing registration.py and instead just initializing the environment on the main file, like the examples in the petting zoo:

from tutorial3_action_masking import CustomEnvironment

from pettingzoo.test import parallel_api_test

if __name__ == "__main__":
    env = CustomEnvironment()
    parallel_api_test(env, num_cycles=1_000_000)

There's no longer support for registration. This doesn't seem really necessary? But maybe I'm missing something and we should support registration ourselves?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions