Code coverage measurement for Python

Edit Package python-coverage
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.

Refresh
Refresh
Source Files
Filename Size Changed
coverage-7.5.3.tar.gz 0000786184 768 KB
python-coverage.changes 0000063394 61.9 KB
python-coverage.spec 0000003955 3.86 KB
Latest Revision
Ana Guerrero's avatar Ana Guerrero (anag+factory) accepted request 1178912 from Dirk Mueller's avatar Dirk Mueller (dirkmueller) (revision 63)
- update to 7.5.3:
  * Performance improvements for combining data files, especially
    when measuring line coverage. A few different quadratic
    behaviors were eliminated. In one extreme case of combining
    700+ data files, the time dropped from more than three hours
    to seven minutes.  Thanks for Kraken Tech for funding the
    fix.
  * Performance improvements for generating HTML reports, with a
    side benefit of reducing memory use, closing issue 1791.
    Thanks to Daniel Diniz for helping to diagnose the problem.
  * Fix: nested matches of exclude patterns could exclude too
    much code, as reported in issue 1779.  This is now fixed.
  * Changed: previously, coverage.py would consider a module
    docstring to be an executable statement if it appeared after
    line 1 in the file, but not executable if it was the first
    line.  Now module docstrings are never counted as executable
    statements.  This can change coverage.py's count of the
    number of statements in a file, which can slightly change the
    coverage percentage reported.
  * In the HTML report, the filter term and "hide covered"
    checkbox settings are remembered between viewings, thanks to
    Daniel Diniz.
  * Python 3.13.0b1 is supported.
  * Fix: parsing error handling is improved to ensure bizarre
    source files are handled gracefully, and to unblock oss-fuzz
    fuzzing, thanks to Liam DeVoe. Closes issue 1787.
Comments 0
openSUSE Build Service is sponsored by