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:
status
2024-03-29: configman is an unmaintained project.
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 to run all the unit tests and tox to test multiple python versions. To run the whole suite just run:
toxwill pass arguments after--tonosetests. To run with test coverage calculation, runtoxlike this:If you want to run a specific test in a testcase class, though, you might consider just using
nosetests:Making a release
Because our
.travis.ymlhas 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 theconfigman/version.txtfile. Suppose you make some changes: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:
After that travis, upon a successful build will automatically make a new tarball and wheel and upload it to PyPI