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

Add plugin system for third-party environments #2383

Merged
merged 1 commit into from
Sep 15, 2021
Merged

Add plugin system for third-party environments #2383

merged 1 commit into from
Sep 15, 2021

Conversation

JesseFarebro
Copy link
Contributor

Most of the discussion is at #2345.

This is a reference implementation of this system. One major thing has changed from #2345. Instead of having a blank key for internal environments (which actually isn't possible), I have two entry points.

  1. gym.envs for all third-party environments with strict namespacing imposed on registration.
  2. gym.envs.internal for packages that are part of a whitelist (e.g., ale-py) which can register into the root namespace, i.e., there are no namespace restrictions imposed.

Thoughts?

@pzhokhov
Copy link
Collaborator

pzhokhov commented Oct 6, 2021

I like this; but I think some documentation (for folks implementing 3rd party environments) is needed. As it stands, the details on how to interact with the plugin system are buried in #2345.

@jkterry1
Copy link
Collaborator

jkterry1 commented Oct 7, 2021

@pzhokhov A documentation website is under active development

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 this pull request may close these issues.

3 participants