Quick way to store db connection details out of sources.
import configdb import ooop ooop.OOOP( configdb.configdb(required=”user pwd dbname”) )
By default, attributes are taken from a YAML file at system defined user configuration location. From the key (profile) ‘default’. If the file is not there, it is created with a yaml file with null values. You have to fill them.
To change the profile you can use the ‘profile’ keyword or DBCONFIG_PROFILE environ.
Metadata
Release files for configdb 0.1
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 |
|---|---|---|---|---|
| configdb-0.1.tar.gz | 3.2 kB | Without provenance | Details for configdb-0.1.tar.gz |
Release files / configdb-0.1.tar.gz
| Download URL | configdb-0.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52aed5844c0663ca71bde4f453227df13a7dfa7f07237b1ae782182e18ec9927
|
|
BLAKE2b-256 checksum How to use checksums |
be6d292f24bc8442fb395386ae03892cd82a0ee7b00424d5f14b32186babcc0e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for configdb 0.1
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.