Update coverage to 7.6.10

[pyup-bot]

This PR updates coverage from 7.6.7 to 7.6.10.

Changelog

7.6.10

---------------------------

- Fix: some descriptions of missing branches in HTML and LCOV reports were
incorrect when multi-line statements were involved (`issue 1874`_ and `issue
1875`_).  These are now fixed.

- Fix: Python 3.14 `defers evaluation of annotations <pep649_>`_ by moving them
into separate code objects.  That code is rarely executed, so coverage.py
would mark them as missing, as reported in `issue 1908`_.  Now they are
ignored by coverage automatically.

- Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
mocks, imports, and trace functions: `issue 1902`_.  To be honest, I don't
understand the problem or the solution, but ``git bisect`` helped find it,
and now it's fixed.

- Docs: re-wrote the :ref:`subprocess` page to put multiprocessing first and to
highlight the correct use of :class:`multiprocessing.Pool
<python:multiprocessing.pool.Pool>`.

.. _issue 1874: https://github.com/nedbat/coveragepy/issues/1874
.. _issue 1875: https://github.com/nedbat/coveragepy/issues/1875
.. _issue 1902: https://github.com/nedbat/coveragepy/issues/1902
.. _issue 1908: https://github.com/nedbat/coveragepy/issues/1908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-annotations


.. _changes_7-6-9:

7.6.9

--------------------------

- Fix: `Tomas Uribe fixed <pull 1901_>`_ a performance problem in the XML
report.  Large code bases should produce XML reports much faster now.

.. _pull 1901: https://github.com/nedbat/coveragepy/pull/1901


.. _changes_7-6-8:

7.6.8

--------------------------

- Fix: the LCOV report code assumed that a branch line that took no branches
meant that the entire line was unexecuted.  This isn't true in a few cases:
the line might always raise an exception, or might have been optimized away.
Fixes `issue 1896`_.

- Fix: similarly, the HTML report will now explain that a line that jumps to
none of its expected destinations must have always raised an exception.
Previously, it would say something nonsensical like, "line 4 didn't jump to
line 5 because line 4 was never true, and it didn't jump to line 7 because
line 4 was always true."  This was also shown in `issue 1896`_.

.. _issue 1896: https://github.com/nedbat/coveragepy/issues/1896


.. _changes_7-6-7:

Links

• PyPI: https://pypi.org/project/coverage
• Changelog: https://data.safetycli.com/changelogs/coverage/
• Repo: https://github.com/nedbat/coveragepy