A simple Python configuration file operator
This project provides a common way to read configurations.
Installation
It is possible to install the tool with pip:
pip install sc-config
Configuration
Configuration files reading in this order, the first is the top most priority: 1. production.xml in current directory, 2. production.xml in <project_name> directory under User directory, 3. production.xml in <project_name> directory under /var/opt/sc/ directory, 4. default.xml in <project_name> directory under /var/opt/sc/ directory.
Dependencies
ruamel.yaml>=0.17.17
Jinja2 >= 2.0
Cerberus >= 1.3.1
MarkupSafe>=2.0.1
License
The script is released under the MIT License. The MIT License is registered with and approved by the Open Source Initiative.
1 maintainer
Metadata
1 maintainer
Release files for sc-config 0.0.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sc_config-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Release files / sc_config-0.0.15-py3-none-any.whl
| Download URL | sc_config-0.0.15-py3-none-any.whl |
|---|---|
| Size | 20.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
93a1f78f610ce32ae4887615d8befd3a1d830d451aed5dc0618c2db535fd4076
|
|
BLAKE2b-256 checksum How to use checksums |
248b148afc944d383b9de30e47871a9b9de5684569b55e90729564eca106318a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.21
|
Security for sc-config 0.0.15
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.
