You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For new users (as I am) it might be hard to navigate the registry - it is not immediately obvious where and how a component is instantiated. Also, it might be challenging to maintain multiple registries in large projects.
This object instantiation approach does not require any registration and can instantiate any object from any library that is installed in the same python environment.
Additionally, it can be extended to handle partial functions and many more.
What is your opinion on that? I can implement a small example demoing this instantiation
Any other context?
No response
The text was updated successfully, but these errors were encountered:
What is the feature?
For new users (as I am) it might be hard to navigate the registry - it is not immediately obvious where and how a component is instantiated. Also, it might be challenging to maintain multiple registries in large projects.
An alternative approach to instantiation is to use the python path to a component (class, function, ...) as e.g. done here https://github.com/Farama-Foundation/HighwayEnv/blob/master/highway_env/utils.py#L38
Applying the approach from
highway-env
, instantiating from config could look as followswith
This object instantiation approach does not require any registration and can instantiate any object from any library that is installed in the same python environment.
Additionally, it can be extended to handle partial functions and many more.
What is your opinion on that? I can implement a small example demoing this instantiation
Any other context?
No response
The text was updated successfully, but these errors were encountered: