python-alkivi-config-manager
Python config-manager used at Alkivi
Package
Example
Write a conf like
[default]
; general configuration: default endpoint
endpoint=dev
[dev]
; configuration specific to 'dev' endpoint
env=dev
[prod]
; configuration specific to 'prod' endpoint
env=prodfrom alkivi.config import ConfigManager
config = ConfigManager('test')
# This will look for several files, in order
# 1. Current working directory: ``./test.conf``
# 2. Current user's home directory ``~/.test.conf``
# 3. System wide configuration ``/etc/test.conf``
# Then find the endpoint
endpoint = config.get('default', endpoint)
# Or use a specific one
endpoint = 'prod'
# And then
env = config.get(endpoint, 'env')Parameters
Tests
Testing is set up using pytest and coverage is handled with the pytest-cov plugin.
Run your tests with py.test in the root directory.
Coverage is ran by default and is set in the pytest.ini file. To see an html output of coverage open htmlcov/index.html after running the tests.
TODO
Travis CI
There is a .travis.yml file that is set up to run your tests for python 2.7 and python 3.2, should you choose to use it.
TODO
2 maintainers
Metadata
2 maintainers
Release files for alkivi-config-manager 1.2.9
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 |
|---|---|---|---|---|
| alkivi_config_manager-1.2.9-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / alkivi_config_manager-1.2.9-py2.py3-none-any.whl
| Download URL | alkivi_config_manager-1.2.9-py2.py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4c1d31412c8de90f4ea69552bccd772bfff8a8bee017a074777515c6910152b7
|
|
BLAKE2b-256 checksum How to use checksums |
5ce0cb703b45002c5b34f973ba6b62e9077e69840bfbebf2384d49cfc6f44413
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for alkivi-config-manager 1.2.9
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.
