prettyconf
Pretty Conf is a Python library created to make easy the separation of configuration and code following the recommendations of 12 Factor’s topic about configs.
It is strongly inspired in python-decouple and both provides a similar API. It is framework agnostic and works the same way under Django, Flask, FastAPI or a plain command line script.
Installation
pip install prettyconfThe AwsParameterStore loader depends on boto3. Install the optional aws feature if you need it:
pip install prettyconf[aws]prettyconf requires Python 3.10 or newer.
Documentation
You can find prettyconf documentation at Read the Docs website.
Development
The project uses uv and a Makefile as its entry point. make setup bootstraps everything, installing uv first if it is missing:
make setupThe remaining targets are listed by make help:
make test |
run the test suite (ARGS="-k name" to filter) |
make test-all |
run the test suite on every supported python |
make coverage |
run the test suite with a coverage report |
make lint |
check the code with ruff |
make format |
reformat and auto-fix the code with ruff |
make typecheck |
check the types with ty |
make docs |
build the HTML documentation |
make build |
build the sdist and the wheel |
make update-deps |
upgrade every dependency and refresh uv.lock |
Any target accepts a PYTHON variable to run against another supported interpreter, each one in its own virtualenv:
make test PYTHON=3.10Pull requests should keep make lint, make typecheck and make test passing, and should describe the change well enough that a reviewer does not need to open the linked issue. Releases are published to PyPI by GitHub Actions when a GitHub release is created, which is what make release does.
1 maintainer
Metadata
1 maintainer
Release files for prettyconf 3.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 | |
|---|---|---|---|---|
| prettyconf-3.0.1.tar.gz | 30.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| prettyconf-3.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.3 kB
Release files / prettyconf-3.0.1.tar.gz
| Download URL | prettyconf-3.0.1.tar.gz |
|---|---|
| Size | 30.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0604e2046346ffa4c69fd56e428e45b980c6ad6d618540ab5dfc73dbc31b8f46
|
|
BLAKE2b-256 checksum How to use checksums |
f27859fa76870a0ee304f696e530807a4833eaed0aa8fbca93b09c7a70efc6b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 4, 2026.
Transparency logRelease files / prettyconf-3.0.1-py3-none-any.whl
| Download URL | prettyconf-3.0.1-py3-none-any.whl |
|---|---|
| Size | 11.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e7a2e0c50076c94b918749d0109b6cc51667202c0511553b628cbe4290edee8
|
|
BLAKE2b-256 checksum How to use checksums |
72b25b60479a992c74db87501a1f7a9dfa4fd621415a0390b013bbd53387a451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Aug 4, 2026.
Transparency logSecurity for prettyconf 3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for prettyconf-3.0.1.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 Aug 4, 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.
