elib-config 2018.11.12.1

My own poor little attempt at a config lib

README

elib_config

[](https://github.com/ellerbrock/open-source-badges/)

[](https://pypi.python.org/pypi/elib_config/) [](https://github.com/etcher-be/elib_config/blob/master/LICENSE) [](https://ci.appveyor.com/project/132nd-etcher/elib-config) [](https://www.codacy.com/app/etcher-be/elib_config) [](https://www.codacy.com/app/etcher-be/elib_config) [](https://requires.io/github/etcher-be/elib_config/requirements/?branch=master) [](https://codeclimate.com/github/etcher-be/elib_config) [](https://bettercodehub.com/results/etcher-be/elib_config) [](https://bestpractices.coreinfrastructure.org/projects/2145) [](https://www.codefactor.io/repository/github/etcher-be/elib_config)

[](https://waffle.io/etcher-be/elib_config/metrics/throughput)

My own poor little attempt at a config lib.

I want configuration to live in a TOML file (maybe PEP518 will take off, and I’d like to give TOML a try anyway).

I also want config values set in the OS environment to take precedence.

I want config values to exist in a hierarchic tree.

I want config values to be type-checked, and casted to the correct type at runtime. Obviously, those types must be checked.

I want config values with default values, and config values without. Those without should be considered “mandatory” config values.

All of those checks must raise corresponding exceptions.

Finally, since configuration evolves with the package, it’s hard to keep track of. Therefore, I want the config package to create an example config file based on the config values that have been declared, and nothing else.

This package does about all that, hopefully in a consistent way.