Discoverability for nested environment library integrations
Open
Nobody has claimed this yet.
CLI
env-integration
needs-design
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 318
Description
Environment library integrations yield many possible environments to use through Gym, but unless there is an explicit config present in Gym for each environment in the library, the supported environments aren't discoverable
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how Gym discovers environment library integrations and where explicit per-environment configuration is defined. Trace a nested integration from registration to the list of supported environments; done means environments provided by the library are discoverable without adding an explicit Gym config for each one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100