Version 3.7 — 2013-10-06
- Added the
--debugswitch tocoverage run. It accepts a list of options indicating the type of internal activity to log to stderr. - Improved the branch coverage facility, fixing issue 92 and issue 175.
- Running code with
coverage run -mnow behaves more like Python does, setting sys.path properly, which fixes issue 207 and issue 242. - Coverage.py can now run .pyc files directly, closing issue 264.
- Coverage.py properly supports .pyw files, fixing issue 261.
- Omitting files within a tree specified with the
sourceoption would cause them to be incorrectly marked as un-executed, as described in issue 218. This is now fixed. - When specifying paths to alias together during data combining, you can now specify relative paths, fixing issue 267.
- Most file paths can now be specified with username expansion (
~/src, or~build/src, for example), and with environment variable expansion (build/$BUILDNUM/src). - Trying to create an XML report with no files to report on, would cause a ZeroDivisionError, but no longer does, fixing issue 250.
- When running a threaded program under the Python tracer, coverage.py no longer issues a spurious warning about the trace function changing: “Trace function changed, measurement is likely wrong: None.” This fixes issue 164.
- Static files necessary for HTML reports are found in system-installed places, to ease OS-level packaging of coverage.py. Closes issue 259.
- Source files with encoding declarations, but a blank first line, were not decoded properly. Now they are. Thanks, Roger Hu.
- The source kit now includes the
__main__.pyfile in the root coverage directory, fixing issue 255.
➡️ PyPI page: coverage 3.7.
➡️ To install: python3 -m pip install coverage==3.7