Version 7.11.1 — 2025-11-07
- Fix: if the measurement core defaults to “sysmon” (the default for Python 3.14+ since v7.9.1), but sysmon can’t support some aspect of your configuration (concurrency settings, dynamic contexts, and so on), then the ctrace core is used instead. Previously, this would result in an error. Now a warning is issued instead, explaining the fallback. An explicit request for sysmon with conflicting settings will still result in an error. Closes issue 2064.
- Fix: some multi-line case clauses or for loops (and probably other constructs) could cause incorrect claims of missing branches with the sys.monitoring core, as described in issue 2070. This is now fixed.
- Fix: when running in pytest under coverage, a
breakpoint()would stop in the wrong frame, one level down from where it should, as described in issue 1420. This was due to a coverage change in v6.4.1 that seemed to give a slight performance improvement, but I couldn’t reproduce the performance gain, so it’s been reverted, fixing the debugger problem. - A new debug option
--debug=coreshows which core is in use and why. - Split
sqlitedebugging information out of thesyscoverage debug and --debug option options since it’s bulky and not very useful. - Updated the How coverage.py works page to better describe the three different measurement cores.
➡️ PyPI page: coverage 7.11.1.
➡️ To install: python3 -m pip install coverage==7.11.1