- Fulll Documentation
- Repository
- PyPI
Rationale
Configuration values are usually found on well defined locations. On Linux systems this is usually /etc or the home folder. The code for finding these config files is always the same. But finding config files can be more interesting than that:
If config files contain passwords, the application should issue appropriate warnings if it encounters an insecure file and refuse to load it.
The expected structure in the config file can be versioned (think: schema). If an application is upgraded and expects new values to exist in an old version file, it should notify the user.
It should be possible to override the configuration on a per installed instance, even per-execution.
config_resolver tackles all these challenges in a simple-to-use drop-in module. The module uses no additional external modules (no additional dependencies, pure Python).
Additionally, the existing “default values” mechanisms in Python is broken, in that cannot have two different default values for the same variable name in two different sections.
1 maintainer
Metadata
1 maintainer
Release files for config-resolver 4.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| config_resolver-4.0.0.tar.gz | 5.7 kB | Details |
Release files / config_resolver-4.0.0.tar.gz
| Download URL | config_resolver-4.0.0.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a26457fa42d14e80d9c167732e53d9a324fd5450c5fb288c99d7b1ab869edbce
|
|
BLAKE2b-256 checksum How to use checksums |
e3427a36ad6de0ff726fe31ae09495f6bb84c6f0fddf34387cea553aa90cb4ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
