config_resolver
- Full Documentation
- Repository
- PyPI
config_resolver provides a simple, yet flexible way to provide configuration to your applications. It follows the XDG Base Dir Spec (This instance is based on 0.8 of this spec) for config file locations, and adds additional ways to override config locations. The aims of this package are:
Provide a simple API
Follow well-known standards for config-file locations
Be as close to pure-Python as possible
Be framework agnostic
Allow custom configutaion types (.ini and .json support is shipped by default)
Allow to provide system-wide defaults but allow overriding of values for more specific environments. These are (in increasing order of specificity):
System-wide configuration (potentially requiring root-access to modify)
User-level configuration (for all instances running as that user)
Current Working Directory configuration (for a running instance)
Per-Instance configuration
1 maintainer
Metadata
1 maintainer
Release files for config-resolver 5.2.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 | Provenance | Actions |
|---|---|---|---|---|
| config_resolver-5.2.0.tar.gz | 17.6 kB | With provenance | Details for config_resolver-5.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| config_resolver-5.2.0-py3-none-any.whl | Python 3 | none | any | Details for config_resolver-5.2.0-py3-none-any.whl |
Total release size: 31.8 kB
Release files / config_resolver-5.2.0.tar.gz
| Download URL | config_resolver-5.2.0.tar.gz |
|---|---|
| Size | 17.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bca0ebcf73adfba8da6da4a70c735796aedfd2a4fe4be99178b80971dfdbe28f
|
|
BLAKE2b-256 checksum How to use checksums |
b49b9a5f90f1c6239798076f961250a670aa563192762b807417a5c3d46a88bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logRelease files / config_resolver-5.2.0-py3-none-any.whl
| Download URL | config_resolver-5.2.0-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
737f40920d842ca9ca00e67bb3a284355b12864aa486b12f72a555241f02d6c5
|
|
BLAKE2b-256 checksum How to use checksums |
d83fadabd285f5f833a01470d317da9bd9872036564f00f39410a26909878b83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logSecurity for config-resolver 5.2.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for config_resolver-5.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.
Transparency logA 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.
