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.

➡️  PyPI page: coverage 7.5.3.
➡️  To install: python3 -m pip install coverage==7.5.3

7.5.2

• 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.

➡️  PyPI page: coverage 7.5.2.
➡️  To install: python3 -m pip install coverage==7.5.2

7.5.1

• Fix: a pragma comment on the continuation lines of a multi-line statement now excludes the statement and its body, the same as if the pragma is on the first line. This closes issue 754. The fix was contributed by Daniel Diniz.
• Fix: very complex source files like this one could cause a maximum recursion error when creating an HTML report. This is now fixed, closing issue 1774.
• HTML report improvements:
  • Support files (JavaScript and CSS) referenced by the HTML report now have hashes added to their names to ensure updated files are used instead of stale cached copies.
  • Missing branch coverage explanations that said "the condition was never false" now read "the condition was always true" because it's easier to understand.
  • Column sort order is remembered better as you move between the index pages, fixing issue 1766. Thanks, Daniel Diniz.

➡️  PyPI page: coverage 7.5.1.
➡️  To install: python3 -m pip install coverage==7.5.1

7.5.0

• Added initial support for function and class reporting in the HTML report. There are now three index pages which link to each other: files, functions, and classes. Other reports don't yet have this information, but it will be added in the future where it makes sense. Feedback gladly accepted! Finishes issue 780.
• Other HTML report improvements:
  • There is now a "hide covered" checkbox to filter out 100% files, finishing issue 1384.
  • The index page is always sorted by one of its columns, with clearer indications of the sorting.
  • The "previous file" shortcut key didn't work on the index page, but now it does, fixing issue 1765.
• The debug output showing which configuration files were tried now shows absolute paths to help diagnose problems where settings aren't taking effect, and is renamed from "attempted_config_files" to the more logical "config_files_attempted."
• Python 3.13.0a6 is supported.

➡️  PyPI page: coverage 7.5.0.
➡️  To install: python3 -m pip install coverage==7.5.0

7.4.4

• Fix: in some cases, even with [run] relative_files=True, a data file could be created with absolute path names. When combined with other relative data files, it was random whether the absolute file names would be made relative or not. If they weren't, then a file would be listed twice in reports, as detailed in issue 1752. This is now fixed: absolute file names are always made relative when combining. Thanks to Bruno Rodrigues dos Santos for support.
• Fix: the last case of a match/case statement had an incorrect message if the branch was missed. It said the pattern never matched, when actually the branch is missed if the last case always matched.
• Fix: clicking a line number in the HTML report now positions more accurately.
• Fix: the report:format setting was defined as a boolean, but should be a string. Thanks, Tanaydin Sirin. It is also now documented on the configuration page <config_report_format>.

➡️  PyPI page: coverage 7.4.4.
➡️  To install: python3 -m pip install coverage==7.4.4

7.4.3

• Fix: in some cases, coverage could fail with a RuntimeError: "Set changed size during iteration." This is now fixed, closing issue 1733.

➡️  PyPI page: coverage 7.4.3.
➡️  To install: python3 -m pip install coverage==7.4.3

7.4.2

• Fix: setting COVERAGE_CORE=sysmon no longer errors on 3.11 and lower, thanks Hugo van Kemenade. It now issues a warning that sys.monitoring is not available and falls back to the default core instead.

➡️  PyPI page: coverage 7.4.2.
➡️  To install: python3 -m pip install coverage==7.4.2

7.4.1

• Python 3.13.0a3 is supported.
• Fix: the JSON report now includes an explicit format version number, closing issue 1732.

➡️  PyPI page: coverage 7.4.1.
➡️  To install: python3 -m pip install coverage==7.4.1

7.4.0

• In Python 3.12 and above, you can try an experimental core based on the new sys.monitoring <python:sys.monitoring> module by defining a COVERAGE_CORE=sysmon environment variable. This should be faster for line coverage, but not for branch coverage, and plugins and dynamic contexts are not yet supported with it. I am very interested to hear how it works (or doesn't!) for you.

➡️  PyPI page: coverage 7.4.0.
➡️  To install: python3 -m pip install coverage==7.4.0

7.3.4

• Fix: the change for multi-line signature exclusions in 7.3.3 broke other forms of nested clauses being excluded properly. This is now fixed, closing issue 1713.
• Fix: in the HTML report, selecting code for copying won't select the line numbers also. Thanks, Robert Harris.

➡️  PyPI page: coverage 7.3.4.
➡️  To install: python3 -m pip install coverage==7.3.4