Log message:
py-coverage: updated to 7.4.3

Version 7.4.3 — 2024-02-23

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

Log message:
py-coverage: updated to 7.4.2

Version 7.4.2 — 2024-02-20

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

Log message:
py-coverage: updated to 7.4.1

Version 7.4.1 — 2024-01-26

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

Log message:
py-coverage: updated to 7.4.0

Version 7.4.0 — 2023-12-27

- 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, though
  plugins and dynamic contexts are not yet supported with it.  I am very
  interested to hear how it works (or doesn't!) for you.

Log message:
py-coverage: updated to 7.3.3

Version 7.3.3 — 2023-12-14
--------------------------

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

Log message:
py-coverage: fix PLIST

Log message:
python/wheel.mk: simplify a lot, and switch to 'installer' for installation

This follows the recommended bootstrap method (flit_core, build, installer).

However, installer installs different files than pip, so update PLISTs
for all packages using wheel.mk and bump their PKGREVISIONs.

Log message:
py-coverage: updated to 7.3.2

Version 7.3.2 — 2023-10-02
--------------------------

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

Log message:
py-coverage: updated to 7.3.1

Version 7.3.1 — 2023-09-06
--------------------------
- 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
  <starbad_>`_, who `provided patient detailed diagnosis <pull \ 
1650_>`_ and
  graciously agreed to a pragmatic resolution.

- The API docs were missing from the last version. They are now `restored
  <apidocs_>`_.

Log message:
py-coverage: updated to 7.3.0

Version 7.3.0 — 2023-08-12

Added a Coverage.collect() context manager to start and stop coverage data \ 
collection.
Dropped support for Python 3.7.
Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode. \ 
Coverage.py would fail with the error Safety level may not be changed inside a \ 
transaction. This is now avoided, closing issue 1646. Thanks to Michael Bell for \ 
the detailed bug report.
Docs: examples of configuration files now include separate examples for the \ 
different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.
Fix: added nosemgrep comments to our JavaScript code so that semgrep-based SAST \ 
security checks won’t raise false alarms about security problems that aren’t \ 
problems.
Added a CITATION.cff file, thanks to Ken Schackart.