Right now, config.py is imported from the .../lib/. folder, which cannot be maintained/documented through multiple experiments (if they require non-default parameters). What we need is to use the local config file even in repo-located libraries/scripts.
The best way I can think to do this is to create a config class that acts as the namespace, and which we can pass to any methods that need it. This way, we remove the import config.py in each lib and be certain that config parameters are coming through the local config.py file.
[file (location)]
some_script (local) -> loads config.py and creates config class.
some_script (local) -> imports library (repo)
some_script (local) -> calls function from library (repo) and passes the function a copy ofconfig` class.
Right now, config.py is imported from the .../lib/. folder, which cannot be maintained/documented through multiple experiments (if they require non-default parameters). What we need is to use the local config file even in repo-located libraries/scripts.
The best way I can think to do this is to create a
configclass that acts as the namespace, and which we can pass to any methods that need it. This way, we remove theimport config.pyin each lib and be certain that config parameters are coming through the local config.py file.[file (location)]
some_script(local) -> loadsconfig.pyand createsconfigclass.some_script(local) -> imports library (repo)some_script (local) -> calls function from library (repo) and passes the function a copy ofconfig` class.