This module replicates some features from the node.js config module.
Currently supports *.py config files in a config folder in the current working directory. Other features will be added as they become necessary.
testing
docker-compose up will automatically test the project and watch for changes.
To generate html coverage reports run: docker-compose run py tox -e html
To run only the syntax linter run: docker-compose run py tox -e lint
For more advanced testing see the tox.ini file.
Metadata
Release files for sagaconfig 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 |
|---|---|---|---|---|
| sagaconfig-0.0.4.tar.gz | 2.7 kB | Without provenance | Details for sagaconfig-0.0.4.tar.gz |
Release files / sagaconfig-0.0.4.tar.gz
| Download URL | sagaconfig-0.0.4.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3bab103e8be52580c4bdd09e35cdc0d7ef6c95dfea497d3a69c1a5e2e8c257c8
|
|
BLAKE2b-256 checksum How to use checksums |
da370f7701b8adf00388fd22e9f7ee53d85b20b3409744c63ca2398b9c8f5cbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sagaconfig 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.