Skip to main content

README

elib_config

[![<3 Open Source](https://badges.frapsoft.com/os/v3/open-source-200x33.png?v=103)](https://github.com/ellerbrock/open-source-badges/)

[![Cheese shop](https://img.shields.io/pypi/status/elib_config.svg)](https://pypi.python.org/pypi/elib_config/) [![License](https://img.shields.io/github/license/etcher-be/elib_config.svg)](https://github.com/etcher-be/elib_config/blob/master/LICENSE) [![Appveyor build](https://img.shields.io/appveyor/ci/132nd-etcher/elib-config/master.svg?label=master)](https://ci.appveyor.com/project/132nd-etcher/elib-config) [![Codacy grade](https://img.shields.io/codacy/grade/58cb5d65f3644ac790d8463749a350b6.svg)](https://www.codacy.com/app/etcher-be/elib_config) [![Codacy coverage](https://img.shields.io/codacy/coverage/58cb5d65f3644ac790d8463749a350b6.svg)](https://www.codacy.com/app/etcher-be/elib_config) [![Requires.io](https://requires.io/github/etcher-be/elib_config/requirements.svg?branch=master)](https://requires.io/github/etcher-be/elib_config/requirements/?branch=master) [![CodeClimate maintainability](https://img.shields.io/codeclimate/maintainability/etcher-be/elib_config.svg)](https://codeclimate.com/github/etcher-be/elib_config) [![BetterCodeHub](https://bettercodehub.com/edge/badge/etcher-be/elib_config?branch=master)](https://bettercodehub.com/results/etcher-be/elib_config) [![OSI Best Practices](https://bestpractices.coreinfrastructure.org/projects/2145/badge)](https://bestpractices.coreinfrastructure.org/projects/2145) [![CodeFactor](https://www.codefactor.io/repository/github/etcher-be/elib_config/badge)](https://www.codefactor.io/repository/github/etcher-be/elib_config)

[![Throughput Graph](https://graphs.waffle.io/etcher-be/elib_config/throughput.svg)](https://waffle.io/etcher-be/elib_config/metrics/throughput)

My own poor little attempt at a config lib.

I want configuration to live in a TOML file (maybe PEP518 will take off, and I’d like to give TOML a try anyway).

I also want config values set in the OS environment to take precedence.

I want config values to exist in a hierarchic tree.

I want config values to be type-checked, and casted to the correct type at runtime. Obviously, those types must be checked.

I want config values with default values, and config values without. Those without should be considered “mandatory” config values.

All of those checks must raise corresponding exceptions.

Finally, since configuration evolves with the package, it’s hard to keep track of. Therefore, I want the config package to create an example config file based on the config values that have been declared, and nothing else.

This package does about all that, hopefully in a consistent way.

Metadata

Release files for elib-config 2018.12.18.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for elib-config 2018.12.18.1
File Interpreter ABI Platform
elib_config-2018.12.18.1-py3-none-any.whl Python 3 none any Details

Release files / elib_config-2018.12.18.1-py3-none-any.whl

Download URL elib_config-2018.12.18.1-py3-none-any.whl
Size 34.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
54f31f53307ef19335c5e76f8fad219bdbf9a2fa0b6ae34ac6b739fd93a4b4aa
BLAKE2b-256 checksum
How to use checksums
99b2d90ce6cd6f45dc57fd43fb82dcdeb6227bb96b10a833b0541c342b0f91f9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.12.1 pkginfo/1.4.2 requests/2.21.0 setuptools/40.6.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.6.7

Security for elib-config 2018.12.18.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.

Release history Release notifications | RSS feed

This release

2018.12.18.1 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page