Update dependency coverage to >=7.11.3 #274

Merged

tobru merged 1 commit from renovate/coverage-7.x into main

2025-11-10 12:36:25 +00:00

renovate commented

2025-11-08 03:01:41 +00:00

Member

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	`>=7.11.0` -> `>=7.11.3`

Release Notes

coveragepy/coveragepy (coverage)

`v7.11.3`

Compare Source

Fix: the 7.11.1 changes meant that conflicts between a requested measurement
core and other settings would raise an error. This was a breaking change from
previous behavior, as reported in issue 2076_ and issue 2078_.

The previous behavior has been restored: when the requested core conflicts
with other settings, another core is used instead, and a warning is issued.
For contributors: the repo has moved from Ned's nedbat GitHub account_ to
the coveragepy GitHub organization_. The default branch has changed from
master to main.

.. _issue 2076: https://github.com/coveragepy/coveragepy/issues/2076
.. _issue 2078: https://github.com/coveragepy/coveragepy/issues/2078
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

`v7.11.2`

Compare Source

Fix: using the "sysmon" measurement core in 7.11.1, if Python code was
claimed to come from a non-Python file, a NotPython exception could be
raised. This could happen for example with Jinja templates compiled to
Python, as reported in issue 2077_. This is now fixed.
Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: https://github.com/coveragepy/coveragepy/issues/2077

.. _changes_7-11-1:

`v7.11.1`

Compare Source

Fix: some chanages to details of how the measurement core is chosen, and how
conflicting settings are handled. The "sysmon" core cannot be used with some
conurrency settings, with dynamic context, and in Python 3.12/3.13, with
branch measurement.
- If the core is not specified and defaults to "sysmon" (Python 3.14+), but
  other settings conflict with sysmon, then the "ctrace" core will be used
  instead with no warning. For concurrency conflicts, this used to produce an
  error, as described in issue 2064_.
- If the "sysmon" core is explicitly requested in your configuration, but
  other settings conflict, an error is now raised. This used to produce a
  warning.
Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in issue 2070_. This is now fixed.
Fix: when running in pytest under coverage, a breakpoint() would stop in
the wrong frame, one level down from where it should, as described in issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give a
slight performance improvement, but I couldn't reproduce the performance
gain, so it's been reverted, fixing the debugger problem.
A new debug option --debug=core shows which core is in use and why.
Split sqlite debugging information out of the sys :ref:coverage debug <cmd_debug> and :ref:cmd_run_debug options since it's bulky and not
very useful.
Updated the :ref:howitworks page to better describe the three different
measurement cores.

.. _issue 1420: https://github.com/coveragepy/coveragepy/issues/1420
.. _issue 2064: https://github.com/coveragepy/coveragepy/issues/2064
.. _issue 2070: https://github.com/coveragepy/coveragepy/issues/2070

.. _changes_7-11-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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [coverage](https://github.com/coveragepy/coveragepy) | `>=7.11.0` -> `>=7.11.3` | [![age](https://developer.mend.io/api/mc/badges/age/pypi/coverage/7.11.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/coverage/7.11.0/7.11.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>coveragepy/coveragepy (coverage)</summary> ### [`v7.11.3`](https://github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7113--2025-11-09) [Compare Source](https://github.com/coveragepy/coveragepy/compare/7.11.2...7.11.3) - Fix: the 7.11.1 changes meant that conflicts between a requested measurement core and other settings would raise an error. This was a breaking change from previous behavior, as reported in `issue 2076`\_ and `issue 2078`\_. The previous behavior has been restored: when the requested core conflicts with other settings, another core is used instead, and a warning is issued. - For contributors: the repo has moved from Ned's `nedbat GitHub account`\_ to the `coveragepy GitHub organization`\_. The default branch has changed from master to main. .. \_issue 2076: https://github.com/coveragepy/coveragepy/issues/2076 .. \_issue 2078: https://github.com/coveragepy/coveragepy/issues/2078 .. \_nedbat GitHub account: https://github.com/nedbat .. \_coveragepy GitHub organization: https://github.com/coveragepy .. \_changes\_7-11-2: ### [`v7.11.2`](https://github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7112--2025-11-08) [Compare Source](https://github.com/coveragepy/coveragepy/compare/7.11.1...7.11.2) - Fix: using the "sysmon" measurement core in 7.11.1, if Python code was claimed to come from a non-Python file, a `NotPython` exception could be raised. This could happen for example with Jinja templates compiled to Python, as reported in `issue 2077`\_. This is now fixed. - Doc: corrected the first entry in the 7.11.1 changelog. .. \_issue 2077: https://github.com/coveragepy/coveragepy/issues/2077 .. \_changes\_7-11-1: ### [`v7.11.1`](https://github.com/coveragepy/coveragepy/blob/HEAD/CHANGES.rst#Version-7111--2025-11-07) [Compare Source](https://github.com/coveragepy/coveragepy/compare/7.11.0...7.11.1) - Fix: some chanages to details of how the measurement core is chosen, and how conflicting settings are handled. The "sysmon" core cannot be used with some conurrency settings, with dynamic context, and in Python 3.12/3.13, with branch measurement. - If the core is not specified and defaults to "sysmon" (Python 3.14+), but other settings conflict with sysmon, then the "ctrace" core will be used instead with no warning. For concurrency conflicts, this used to produce an error, as described in `issue 2064`\_. - If the "sysmon" core is explicitly requested in your configuration, but other settings conflict, an error is now raised. This used to produce a warning. - Fix: some multi-line case clauses or for loops (and probably other constructs) could cause incorrect claims of missing branches with the sys.monitoring core, as described in `issue 2070`\_. This is now fixed. - Fix: when running in pytest under coverage, a `breakpoint()` would stop in the wrong frame, one level down from where it should, as described in `issue 1420`\_. This was due to a coverage change in v6.4.1 that seemed to give a slight performance improvement, but I couldn't reproduce the performance gain, so it's been reverted, fixing the debugger problem. - A new debug option `--debug=core` shows which core is in use and why. - Split `sqlite` debugging information out of the `sys` :ref:`coverage debug <cmd_debug>` and :ref:`cmd_run_debug` options since it's bulky and not very useful. - Updated the :ref:`howitworks` page to better describe the three different measurement cores. .. \_issue 1420: https://github.com/coveragepy/coveragepy/issues/1420 .. \_issue 2064: https://github.com/coveragepy/coveragepy/issues/2064 .. \_issue 2070: https://github.com/coveragepy/coveragepy/issues/2070 .. \_changes\_7-11-0: </details> --- ### 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 has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).