CnfRM
Imagine: an ORM for config
This library lets you declare your config in a way you might know from popular ORM's.
You get
- expressive configuration declaration
- popular fileformats (json, yml?)
- command line options
- env configuration variables
import cnfrm
class MyConf(cnfrm.Config):
name = cnfrm.Field("no name")
size = cnfrm.IntegerField(required=False)
path = cnfrm.DirectoryField(required=False)
email = cnfrm.EmailField(required=False)
filename = cnfrm.FileField()
# create a config instance
config = MyConf()
# start reading things, the later overwrites the former
config.read_env()
config.read_json("~/myconf.json", quiet=True)
config.read_args()
# check if the configuration is complete
config.validate()
# write config to file:
config.write_json("~/myconf.json")
Metadata
Release files for cnfrm 0.2.5
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 | |
|---|---|---|---|---|
| cnfrm-0.2.5.tar.gz | 4.6 kB | Without provenance | Details |
Release files / cnfrm-0.2.5.tar.gz
| Download URL | cnfrm-0.2.5.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00a4c954356cf1949fb7dfdead941c7e982e0ffc160fdb967e262a986667da29
|
|
BLAKE2b-256 checksum How to use checksums |
84ce8921a955a5dc0bc0b13674f435549d5d799120c6f4de249a85fb92641fe8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.3 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.0 CPython/3.9.6
|
Security for cnfrm 0.2.5
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.