v7.4.3

Compare Source

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

.. _issue 1733:https://github.com/nedbat/coveragepy/issues/17333

.. _changes_7-4-2:

v7.4.2

Compare Source

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

.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477

.. _changes_7-4-1:

v7.4.1

Compare Source

• Python 3.13.0a3 is supported.

• Fix: the JSON report now includes an explicit format version number, closing
  issue 1732_.

.. _issue 1732:https://github.com/nedbat/coveragepy/issues/17322

.. _changes_7-4-0:

v7.4.0

Compare Source

• In Python 3.12 and above, you can try an experimental core based on the new
  :mod: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.

.. _changes_7-3-4:

v7.3.4

Compare Source

• 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 <pull 1717_>_.

.. _issue 1713:https://github.com/nedbat/coveragepy/issues/17133
.. _pull 1717https://github.com/nedbat/coveragepy/pull/171717

.. _changes_7-3-3:

v7.3.3

Compare Source

• 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 <pull 1705_>.

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

.. _issue 684:https://github.com/nedbat/coveragepy/issues/6844
.. _pull 1705https://github.com/nedbat/coveragepy/pull/170505
.. _issue 170https://github.com/nedbat/coveragepy/issues/1709709

.. _changes_7-3-2:

v7.3.2

Compare Source

• The coverage lcov command ignored the [report] exclude_lines and
  [report] exclude_also settings (issue 1684). This is now fixed,
  thanks Jacqueline Lee <pull 1685_>.

• 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 <88054_>_ in 2021, and it stopped working completely in Python 3.13.

.. _issue 1605:https://github.com/nedbat/coveragepy/issues/16055
.. _issue 1684https://github.com/nedbat/coveragepy/issues/168484
.. _pull 168https://github.com/nedbat/coveragepy/pull/1685685
.. _880https://github.com/python/cpython/issues/880548054

.. _changes_7-3-1: