All the factory classmethods *write* to environment

[headsrooms]

All the factory classmethods *write* to environment

[headsrooms]

This is the planned behaviour following the twelve-factors' principles: https://12factor.net/config

However, your use case makes sense. I'll see if I can do something about it.

Another option to you is to use the parameter "prefix", then only env vars with the specified prefix will be loaded: https://github.com/kingoodie/configclasses/blob/e9029c967105c192dc79c81913a3f1269353f763/tests/test_configclasses.py#L61

[howardjones]

Hmm, really? I always read that as deliver the config to the app in the environment (like, e.g. docker would), so the app doesn't need to care where it came from. Not load all config inside the app into the environment. What's the config object for, if not that? I think I'll probably write a similar class.

[headsrooms]

Well, I think using the config object is good practice, but sometimes there are situations where it might be more appropriate or cheaper to use the env var, such as when using threads or multiprocessing.