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

7.3.3

• Fix: function definitions with multi-line signatures can now be excluded by matching any of the lines, closing issue 684. Thanks, Jan Rusak, Maciej Kowalczyk and Joanna Ejzel.
• Fix: XML reports could fail with a TypeError if files had numeric components that were duplicates except for leading zeroes, like file1.py and file001.py. Fixes issue 1709.
• The coverage annotate command used to announce that it would be removed in a future version. Enough people got in touch to say that they use it, so it will stay. Don't expect it to keep up with other new features though.
• Added new debug options <cmd_run_debug>:
  • pytest writes the pytest test name into the debug output.
  • dataop2 writes the full data being added to CoverageData objects.

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

7.3.2

• The coverage lcov command ignored the [report] exclude_lines and [report] exclude_also settings (issue 1684). This is now fixed, thanks Jacqueline Lee.
• Sometimes SQLite will create journal files alongside the coverage.py database files. These are ephemeral, but could be mistakenly included when combining data files. Now they are always ignored, fixing issue 1605. Thanks to Brad Smith for suggesting fixes and providing detailed debugging.
• On Python 3.12+, we now disable SQLite writing journal files, which should be a little faster.
• The new 3.12 soft keyword type is properly bolded in HTML reports.
• Removed the "fullcoverage" feature used by CPython to measure the coverage of early-imported standard library modules. CPython stopped using it in 2021, and it stopped working completely in Python 3.13.

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

7.3.1

• The semantics of stars in file patterns has been clarified in the docs. A leading or trailing star matches any number of path components, like a double star would. This is different than the behavior of a star in the middle of a pattern. This discrepancy was identified by Sviatoslav Sydorenko, who provided patient detailed diagnosis and graciously agreed to a pragmatic resolution.
• The API docs were missing from the last version. They are now restored.

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