It is desirable that one can develop their own env without having to work under envpool's code base. While still have the access to register the env with envpool and use the make function to create it. It seems already possible with our current code base, we just need a template repo.
Motivation
It is desirable that one can develop their own env without having to work under envpool's code base. While still have the access to register the env with envpool and use the
make
function to create it. It seems already possible with our current code base, we just need a template repo.Solution
Where
my_private_env
is developed as another package.Checklist
cc @zhongwen