Integrate config.py as function parameter? about atlite HOT 5 CLOSED

My preferred solution would be two-layered:

1. Have an atlite_example.yaml file in the main directory of the repository that the user is supposed to copy to ~/.atlite.yaml.
2. Allow to override the settings there in either the call to instantiate a new Cutout object or its prepare method, as it already is the case for cutout_dir.

Feel free to have a go at it!

from atlite.

I did start working on this, however you mentioned a major update in the next days in #9 .
Does it make sense for me to continue working on thisor are we already taking the redundant road as with ERA5 again? ;-)

from atlite.

Hmm, i have not ripped out config.py just yet.

Ok, I’ll ignore it for now and will just pass everything as arguments explicitly and you will then have to fit your building blocks inside afterwards.

from atlite.

Covered in PR #23 .

from atlite.

Closing: The new version being prepared in #20 will provide a new way of managing the configuration.

from atlite.