Sample config:
# a value is set with: key : value
# values are typed. allowed types are:
# - string (simple or double quotes)
# - boolean (True or False. is case sensitive)
# - integer
strval : 'this is a string'
boolval: True
intval : 142
# you can define hierarchies with dictionaries
# ! no comma to se
orgchart : {
boss : 'Mr Goldmine'
head_office : {
VP : 'Miz dho'
CTO : 'John Bugs'
}
}
Loaded from python:
>>> import pyerconf
>>> cfg = pyerconf.Config('./sample.cfg')
>>> print cfg.strval
this is a string
>>> print cfg.orgchart.boss
Mr Goldmine
>>> print cfg.orgchart.head_office
{'VP': 'Miz dho', 'CTO': 'John Bugs'}
>>> print cfg.foobar
AttributeError
Metadata
Release files for pyerconf 0.1.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 | |
|---|---|---|---|---|
| pyerconf-0.1.0.tar.gz | 16.0 kB | Without provenance | Details |
Release files / pyerconf-0.1.0.tar.gz
| Download URL | pyerconf-0.1.0.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f724cd5b485ef540a0deac3a20e16cae134f8163d8ff31ff1599eaf23aacdf08
|
|
BLAKE2b-256 checksum How to use checksums |
b6f0eea5a19a8d2d1ea462b03e6d85c27e3052f6b5c3b676a538fcf35dcceda5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyerconf 0.1.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.
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.