Divine
Divine is a configuration utility with unique features:
- Ability to chain configs together, composing the whole from pieces
- Ability to quickly grab a nested key using notation like c.get('abc/xyz/foo/bar')
- Integrated f-strings for composable values and DRY patterns
- Auto-callable config entries to instantiate a class or call a function with args and kwargs automatically from the config (yes, this is a security risk; don't parse any config from unknown sources)
Divine accepts YAML or JSON files. It can be manually configured or auto-configured with an environment variable pointing to a config file. This allows for many processes to use the config without having to explicitly initialize the config in each process.
Metadata
Release files for divine 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| divine-0.0.1.tar.gz | 1.4 kB | Without provenance | Details |
Release files / divine-0.0.1.tar.gz
| Download URL | divine-0.0.1.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f52b8f5fb04f3b681b67203e936dc373a56c1300809c557978f102b2c1b82591
|
|
BLAKE2b-256 checksum How to use checksums |
83c002a486b951dce8f4dcf15b8830f5810c3fa380c01f0b6247ccdc436a87f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.29.1 CPython/3.7.1
|
Security for divine 0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.