cb65c644c6
- fix #87 - user versioneer for version management - use tag "vMAJOR.MINOR.PATCH" to indicate release number - exclude generated files from coverage; also exclude tests from coverage reporting; allow use of "# pragma: no cover" to exclude lines of code from coverage - configure coverage with entries in setup.cfg (removed commandline config from workflows/python-package.yml) - related doc updates - make docs automatically use current version (docs use versioneer-based propka.__version__) - also added @IAlibay to authors (forgotten in previous PRs #84 and #85) - generate a sitemap (add sphinx_sitemap to requirements.txt) - add test_version Note: Versioneer-generated version is “0-untagged” on the branch where it is tested so need to add it to a valid result.
Testing PROPKA
These tests assume that PROPKA is installed as a module on your system the
dependencies in ../requirements.txt are satisfied.
If you are running in a virtual environment and want to make changes to your
code, module installation accomplished by
pip install -e .
from the top level of the PROPKA source directory.
Once PROPKA is available as a module, the tests can be run by
python -m pytest tests
either in the top-level directory or tests subdirectory.