configman
[](https://travis-ci.org/mozilla/configman)
Copyright Mozilla, 2013 - 2015
General tool for setting up configuration options per namespaces. Supports reading and writing configs generally from and into config files.
Running tests
We use [nose](http://code.google.com/p/python-nose/) to run all the unit tests and [tox](http://tox.testrun.org/latest/) to test multiple python versions. To run the whole suite just run:
tox
tox will pass arguments after – to nosetests. To run with test coverage calculation, run tox like this:
tox – –with-coverage –cover-html –cover-package=configman
If you want to run a specific test in a testcase class, though, you might consider just using nosetests:
nosetests configman.tests.test_config_manager:TestCase.test_write_flat
Making a release
Because our .travis.yml has all the necessary information to automatically make a release, all you need to do is to push a commit onto master. Most likely you will only want to do this after you have edited the configman/version.txt file. Suppose you make some changes:
git add configman/configman.py git commit -m “fixed something”
You might want to push that to your fork and make a pull request. Then, to update the version and make a release, first do this:
vim configman/version.txt git add configman/version.txt git commit -m “bump to version x.y.z” git push origin master
After that travis, upon a successful build will automatically make a new tarball and wheel and upload it to [PyPI](https://pypi.python.org/pypi/configman)
Metadata
Release files for configman 1.3.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 | Actions |
|---|---|---|---|---|
| configman-1.3.0.tar.gz | 89.8 kB | Without provenance | Details for configman-1.3.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| configman-1.3.0-py3-none-any.whl | Python 3 | none | any | Details for configman-1.3.0-py3-none-any.whl |
| configman-1.3.0-py2-none-any.whl | Python 2 | none | any | Details for configman-1.3.0-py2-none-any.whl |
Total release size: 320.0 kB
Release files / configman-1.3.0.tar.gz
| Download URL | configman-1.3.0.tar.gz |
|---|---|
| Size | 89.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4000037487d65ec05e3d4183298f0a5799d7c71a47e8753f4edeede586baeb50
|
|
BLAKE2b-256 checksum How to use checksums |
0b6c70b79bfeca195fe6debc043c9e5f4dc1de632db527568a151254c1f44d61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / configman-1.3.0-py3-none-any.whl
| Download URL | configman-1.3.0-py3-none-any.whl |
|---|---|
| Size | 115.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8e45c20c7b73173bd4d0194521f982201b70558d6f6e945f11053201110b83e0
|
|
BLAKE2b-256 checksum How to use checksums |
d1451b2a31ca431698674de46259189f0cda3e2570be410aff5a9c14c1e19af3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / configman-1.3.0-py2-none-any.whl
| Download URL | configman-1.3.0-py2-none-any.whl |
|---|---|
| Size | 115.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
bc96b4c974aefabf4605d82dfab409a5aed10b4ae0b05ae2535eda415a3f7b67
|
|
BLAKE2b-256 checksum How to use checksums |
9f8caf9f7931ca363444395f5da0aa4cf118f4e100c10a3a8b7efb56dc64d0de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for configman 1.3.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.