Code coverage measurement for Python
http://pypi.python.org/coverage
Coverage.py measures code coverage, typically during test execution. It uses
the code analysis tools and tracing hooks provided in the Python standard
library to determine which lines are executable, and which have been executed.
- Developed at devel:languages:python
- Sources inherited from project openSUSE:Factory
-
9
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/python-coverage && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| coverage-5.4.tar.gz | 0000687727 672 KB | |
| python-coverage.changes | 0000025323 24.7 KB | |
| python-coverage.spec | 0000004245 4.15 KB |
Revision 44 (latest revision is 62)
Richard Brown (RBrownSUSE)
accepted
request 868480
from
Dirk Mueller (dirkmueller)
(revision 44)
- update to 5.4:
- The text report produced by ``coverage report`` now always outputs a TOTAL
line, even if only one Python file is reported. This makes regex parsing
of the output easier. Thanks, Judson Neer. This had been requested a number
of times
- The ``skip_covered`` and ``skip_empty`` settings in the configuration file
can now be specified in the ``[html]`` section, so that text reports and HTML
reports can use separate settings. The HTML report will still use the
``[report]`` settings if there isn't a value in the ``[html]`` section.
- Combining files on Windows across drives how works properly
- Fix an obscure warning from deep in the _decimal module, as reported in
`issue 1084`_.
- Update to support Python 3.10 alphas in progress, including `PEP 626: Precise
line numbers for debugging and other tools <pep626_>`_.
Comments 0