Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 21, 2025

This PR contains the following updates:

Package Change Age Confidence
coverage 7.8.0 -> 7.10.6 age confidence

Release Notes

nedbat/coveragepy (coverage)

v7.10.6

Compare Source

  • Fix: source directories were not properly communicated to subprocesses
    that ran in different directories, as reported in issue 1499_. This is now
    fixed.

  • Performance: Alex Gaynor continues fine-tuning <pull 2038_>_ the speed of
    combination, especially with many contexts.

.. _issue 1499: #​1499
.. _pull 2038: #​2038

.. _changes_7-10-5:

v7.10.5

Compare Source

  • Big speed improvements for coverage combine: it's now about twice as
    fast! Huge thanks to Alex Gaynor for pull requests 2032 <pull 2032_>,
    2033 <pull 2033_>
    , and 2034 <pull 2034_>_.

.. _pull 2032: #​2032
.. _pull 2033: #​2033
.. _pull 2034: #​2034

.. _changes_7-10-4:

v7.10.4

Compare Source

  • Added patch = fork for times when the built-in forking support is
    insufficient.

  • Fix: patch = execv also inherits the entire coverage configuration now.

.. _changes_7-10-3:

v7.10.3

Compare Source

  • Fixes for patch = subprocess:

    • If subprocesses spawned yet more subprocesses simultaneously, some coverage
      could be missed. This is now fixed, closing issue 2024_.

    • If subprocesses were created in other directories, their data files were
      stranded there and not combined into the totals, as described in issue 2025_. This is now fixed.

    • On Windows (or maybe only some Windows?) the patch would fail with a
      ModuleNotFound error trying to import coverage. This is now fixed,
      closing issue 2022_.

    • Originally only options set in the coverage configuration file would apply
      to subprocesses. Options set on the coverage run command line (such as
      --branch) wouldn't be communicated to the subprocesses. This could
      lead to combining failures, as described in issue 2021_. Now the entire
      configuration is used in subprocesses, regardless of its origin.

    • Added debug=patch to help diagnose problems.

  • Fix: really close all SQLite databases, even in-memory ones. Closes issue 2017_.

.. _issue 2017: #​2017
.. _issue 2021: #​2021
.. _issue 2022: #​2022
.. _issue 2024: #​2024
.. _issue 2025: #​2025

.. _changes_7-10-2:

v7.10.2

Compare Source

  • Fix: some code with NOP bytecodes could report missing branches that are
    actually executed. This is now fixed, closing issue 1999_. Python 3.9
    still shows the problem.

.. _issue 1999: #​1999

.. _changes_7-10-1:

v7.10.1

Compare Source

  • Fix: the exclusion for if TYPE_CHECKING: was wrong: it marked the branch
    as partial, but it should have been a line exclusion so the entire clause
    would be excluded. Improves issue 831_.

  • Fix: changed where .pth files are written for patch = subprocess, closing
    issue 2006_.

.. _issue 2006: #​2006

.. _changes_7-10-0:

v7.10.0

Compare Source

  • A new configuration option: ":ref:config_run_patch" specifies named patches
    to work around some limitations in coverage measurement. These patches are
    available:

    • patch = _exit lets coverage save its data even when :func:os._exit() <python:os._exit> is used to abruptly end the process. This closes
      long-standing issue 310_ as well as its duplicates: issue 312, issue 1673, issue 1845, and issue 1941.

    • patch = subprocess measures coverage in Python subprocesses created
      with :mod:subprocess, :func:os.system, or one of the :func:execv <python:os.execl> or :func:spawnv <python:os.spawnl> family of
      functions. Closes old issue 367, its duplicate issue 378 and old
      issue 689_.

    • patch = execv adjusts the :func:execv <python:os.execl> family of
      functions to save coverage data before ending the current program and
      starting the next. Not available on Windows. Closes issue 43_ after 15
      years!

  • The HTML report now dimly colors subsequent lines in multi-line statements.
    They used to have no color. This gives a better indication of the amount of
    code missing in the report. Closes issue 1308_.

  • Two new exclusion patterns are part of the defaults: ... is automatically
    excluded as a line and if TYPE_CHECKING: is excluded as a branch. Closes
    issue 831_.

  • A new command-line option: --save-signal=USR1 specifies a signal that
    coverage.py will listen for. When the signal is sent, the coverage data will
    be saved. This makes it possible to save data from within long-running
    processes. Thanks, Arkady Gilinsky <pull 1998_>_.

  • A new configuration option: ":ref:config_report_partial_also" is a list of
    regexes to add as pragmas for partial branches. This parallels the
    ":ref:config_report_exclude_also" setting for adding line exclusion
    patterns.

  • A few file path configuration settings didn't allow for tilde expansion:
    :ref:config_json_output, :ref:config_lcov_output and
    :ref:config_run_debug_file. This is now fixed.

  • Wheels are included for 3.14 now that 3.14 rc1 is available.

  • We no longer ship a PyPy-specific wheel. PyPy will install the pure-Python
    wheel. Closes issue 2001_.

  • In the very unusual situation of not having a current frame, coverage no
    longer crashes when using the sysmon core, fixing issue 2005_.

.. _issue 43: #​43
.. _issue 310: #​310
.. _issue 312: #​312
.. _issue 367: #​367
.. _issue 378: #​378
.. _issue 689: #​689
.. _issue 831: #​831
.. _issue 1308: #​1308
.. _issue 1673: #​1673
.. _issue 1845: #​1845
.. _issue 1941: #​1941
.. _pull 1998: #​1998
.. _issue 2001: #​2001
.. _issue 2005: #​2005

.. _changes_7-9-2:

v7.9.2

Compare Source

  • Fix: complex conditionals within a line might cause a KeyError when using
    sys.monitoring, as reported in issue 1991_. This is now fixed.

  • Fix: we can now measure coverage for code in Python archive (.par) files.
    Thanks, Itamer Oren <pull 1984_>_.

.. _pull 1984: #​1984
.. _issue 1991: #​1991

.. _changes_7-9-1:

v7.9.1

Compare Source

  • The "no-ctracer" warning is not issued for Python pre-release versions.
    Coverage doesn't ship compiled wheels for those versions, so this was far too
    noisy.

  • On Python 3.14+, the "sysmon" core is now the default if it's supported for
    your configuration. Plugins and dynamic contexts are still not supported
    with it.

.. _changes_7-9-0:

v7.9.0

Compare Source

  • Added a [run] core configuration setting to specify the measurement core,
    which was previously only available through the COVERAGE_CORE environment
    variable. Finishes issue 1746_.

  • Fixed incorrect rendering of f-strings with doubled braces, closing issue 1980_.

  • If the C tracer core can't be imported, a warning ("no-ctracer") is issued
    with the reason.

  • The C tracer core extension module now conforms to PEP 489, closing issue 1977. Thanks, Adam Turner <pull 1978_>_.

  • Fixed a "ValueError: min() arg is an empty sequence" error caused by strange
    empty modules, found by oss-fuzz_.

.. _issue 1746: #​1746
.. _issue 1977: #​1977
.. _pull 1978: #​1978
.. _issue 1980: #​1980
.. _PEP 489: https://peps.python.org/pep-0489
.. _oss-fuzz: https://google.github.io/oss-fuzz/

.. _changes_7-8-2:

v7.8.2

Compare Source

  • Wheels are provided for Windows ARM64 on Python 3.11, 3.12, and 3.13.
    Thanks, Finn Womack <pull 1972_>_.

.. _issue 1971: #​1971
.. _pull 1972: #​1972

.. _changes_7-8-1:

v7.8.1

Compare Source

  • A number of EncodingWarnings were fixed that could appear if you've enabled
    PYTHONWARNDEFAULTENCODING, fixing issue 1966. Thanks, Henry Schreiner <pull 1967_>.

  • Fixed a race condition when using sys.monitoring with free-threading Python,
    closing issue 1970_.

.. _issue 1966: #​1966
.. _pull 1967: #​1967
.. _issue 1970: #​1970

.. _changes_7-8-0:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 21, 2025
@renovate renovate bot added the dependencies Pull requests that update a dependency file label May 21, 2025
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.8.1 chore(deps): update dependency coverage to v7.8.2 May 23, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 6e93186 to 6437fed Compare May 23, 2025 12:27
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.8.2 chore(deps): update dependency coverage to v7.9.0 Jun 12, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 6437fed to 1bfad07 Compare June 12, 2025 02:32
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.9.0 chore(deps): update dependency coverage to v7.9.1 Jun 13, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 1bfad07 to bea1ca2 Compare June 13, 2025 14:29
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.9.1 chore(deps): update dependency coverage to v7.9.2 Jul 3, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from bea1ca2 to 986648d Compare July 3, 2025 14:57
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.9.2 chore(deps): update dependency coverage to v7.10.0 Jul 24, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 986648d to e45c84e Compare July 24, 2025 20:48
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.0 chore(deps): update dependency coverage to v7.10.1 Jul 27, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from e45c84e to f19c8f9 Compare July 27, 2025 14:49
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.1 chore(deps): update dependency coverage to v7.10.2 Aug 4, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch 2 times, most recently from d42491d to a436587 Compare August 10, 2025 14:27
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.2 chore(deps): update dependency coverage to v7.10.3 Aug 11, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from a436587 to 081661b Compare August 11, 2025 01:54
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.3 chore(deps): update dependency coverage to v7.10.4 Aug 17, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 081661b to 940dfbc Compare August 17, 2025 01:40
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.4 chore(deps): update dependency coverage to v7.10.5 Aug 23, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 940dfbc to 1dad00f Compare August 23, 2025 17:47
@renovate renovate bot changed the title chore(deps): update dependency coverage to v7.10.5 chore(deps): update dependency coverage to v7.10.6 Aug 31, 2025
@renovate renovate bot force-pushed the renovate/coverage-7.x-lockfile branch from 1dad00f to 7c7ab57 Compare August 31, 2025 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants