Log message:
py-coverage: updated to 7.15.4

7.15.4 — 2026-08-06

- Fix: in the HTML report, a source file name containing a double quote (legal
  on POSIX) wasn't escaped where it's dropped into the ``href`` of the index
  and prev/next links, so it could close the attribute early and inject markup.
  Page URLs are now escaped. Thanks, `Rajath Mohare <pull 2227_>`_.

- Fix: the LCOV report wrote file names and other fields into its
  line-oriented records without neutralizing control characters. A measured
  file whose name contained a newline (legal on POSIX) could forge extra
  records, inflating the coverage seen by tools that read the report. Control
  characters in a field are now replaced. Thanks, `Rajath Mohare <pull
  2226_>`_.

- Wheels are now provided for Python 3.15.

Log message:
py-coverage: updated to 7.15.2

7.15.2 — 2026-07-15

- Fix: one of the performance improvements in 7.15.1 (pull 2215) dramatically
  increased memory use during reporting for large projects. Now we use a
  different approach that is both faster and slimmer than 7.15.0. Fixes `issue
  2229`_.

Log message:
py-coverage: updated to 7.15.0

Version 7.15.0 — 2026-07-02

- Since 7.14.0, reporting commands implicitly combine parallel data files. Now
  those commands have a new option ``--keep-combined`` to retain the data files
  after combining them instead of the default, which is to delete them.
  Finishes `issue 2198`_.

- Fix: the LCOV report would incorrectly count excluded functions as uncovered,
  as described in `issue 2205`_. This is now fixed thanks to `Martin Kuntz
  Jacobsen <pull 2206_>`_.

- When running your program, coverage now correctly sets
  ``yourmodule.__spec__.loader`` as `strongly recommended <--loader--_>`_,
  avoiding the deprecation warning described in `issue 2208`_. Thanks, `A5rocks
  <pull 2209_>`_.

- Fix: with Python 3.10, running with the ``-I`` (isolated mode) option didn't
  correctly omit the current directory from the module search path, as
  described in `issue 2103`_. That is now fixed thanks to `Ilia Sorokin <pull
  2211_>`_.

Log message:
py-coverage: updated to 7.14.3

7.14.3 — 2026-06-22

- Fix: the default ``...`` exclusion rule now also matches function bodies
  whose closing return-type bracket is on its own line (for example, after a
  long ``-> dict[ ... ]`` annotation that a formatter has split over multiple
  lines). Closes `issue 2185`_, thanks `Mengjia Shang <pull 2196_>`_.

- Fix: On 3.13t, we incorrectly issued ``Couldn't import C tracer`` errors.
  We can't import the C tracer because in 7.14.2 we stopped shipping compiled
  wheels for 3.13t. Thanks, `Hugo van Kemenade <pull 2203_>`_.

Log message:
py-coverage: updated to 7.14.1

7.14.1

- Fix: the HTML report used typographic niceties to make file paths more
  readable by adding a small amount of space around slashes. Those spaces
  interfered with searching the page for file paths of interest. Now the report
  uses CSS to accomplish the same visual tweak so that searches with slashes
  work correctly. Closes `issue 2170`_.

- `Add a 3.16 PyPI classifier <hugo-316_>`_ since we test on the 3.16 main
  branch.

Log message:
py-coverage: updated to 7.14.0

Version 7.14.0 — 2026-05-10

- Feature: now when running one of the reporting commands, if there are
  parallel data files that need combining, they will be implicitly combined
  before creating the report. There is no option to avoid the combination; let
  us know if you have a use case that requires it.  Thanks, `Tim Hatch
  <pull 2162_>`_. Closes `issue 1781`_.

- Fix: the output from ``combine`` was too verbose, listing each file
  considered. Now it shows a single line with the counts of files combined,
  files skipped, and files with errors. The ``-q`` flag suppresses this line.
  The old detailed lines are available with the new ``--debug=combine`` option.

- Fix: running a Python file through a symlink now sets the sys.path correctly,
  matching regular Python behavior. Fixes `issue 2157`_.

- Fix: ``Collector.flush_data`` could fail with "RuntimeError: Set changed
  size during iteration" when a tracer in another thread added a line to the
  per-file set that ``add_lines`` (or ``add_arcs``) was iterating. The values
  passed to ``CoverageData`` are now snapshotted via ``dict.copy()`` and
  ``set.copy()``, which are atomic under the GIL. Thanks, `Alex Vandiver <pull
  2165_>`_.

- Fix: the soft keyword ``lazy`` is now bolded in HTML reports.

- We are no longer testing eventlet support. Eventlet started issuing stern
  deprecation warnings that break our tests. Our support code is still there.

Log message:
py-coverage: updated to 7.13.5

Version 7.13.5 — 2026-03-17

- Fix: `issue 2138`_ describes a memory leak that happened when repeatedly
  using the Coverage API with in-memory data. This is now fixed.

- Fix: the markdown-formatted coverage report didn't fully escape special
  characters in file paths (`issue 2141`_). This would be very unlikely to
  cause a problem, but now it's done properly, thanks to `Ellie Ayla
  <pull 2142_>`_.

- Fix: the C extension wouldn't build on VS2019, but now it does (`issue
  2145`_).

Log message:
py-coverage: updated to 7.13.4

7.13.4

- Fix: the third-party code fix in 7.13.3 required examining the parent
  directories where coverage was run. In the unusual situation that one of the
  parent directories is unreadable, a PermissionError would occur, as
  described in `issue 2129`_. This is now fixed.

- Fix: in test suites that change sys.path, coverage.py could fail with
  "RuntimeError: Set changed size during iteration" as described and \ 
fixed in
  `pull 2130`_. Thanks, Noah Fatsi.

- We now publish ppc64le wheels, thanks to `Pankhudi Jain <pull 2121_>`_.