pip install importconfig
The special thing about ImportConfig is that it supports a notion
of "imports". You can import other json files in your json file
by specifying a "@file" value at any level in the config and it will
be expanded into that level.
A config file can be loaded lazily and the main config file will only be
loaded once it is called.
**Note:** keys/values defined in the top level document will take precedence
over those loaded in sub-documents.
**Example**::
{
"app_name": "foo",
"logging": {
"@file": "logging.json",
"level": "debug"
}
}
**will translate into**::
{
"app_name": "foo",
"logging": {
"log_file": "/var/log/foo.log",
"level": "debug"
}
}
**Contents of "logging.json"**::
{
"log_file": "/var/log/foo.log",
"level": "info"
}
.. todo::
✓ Support relative paths for ``@file's`` value
✓ Root document take precedence if the same key exists in the imported file
Metadata
Release files for ImportConfig 0.0.4
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 | Actions |
|---|---|---|---|---|
| ImportConfig-0.0.4.tar.gz | 3.4 kB | Without provenance | Details for ImportConfig-0.0.4.tar.gz |
Release files / ImportConfig-0.0.4.tar.gz
| Download URL | ImportConfig-0.0.4.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71bc67606f078cc88a6db7cb8ca41b4110a173cbb835819021fa6e45bb4c7b9f
|
|
BLAKE2b-256 checksum How to use checksums |
8f9b89bdbcf85263a4b26f762fd17b65a24dfed8788fa24d58ea5f030eae6ba3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ImportConfig 0.0.4
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.