Update dependency coverage to v7.11.0 #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==7.6.1->==7.11.0Release Notes
nedbat/coveragepy (coverage)
v7.11.0Compare Source
.. _changes_7-10-7:
v7.10.7Compare Source
Performance: with branch coverage in large files, generating HTML, JSON, or
LCOV reports could take far too long due to some quadratic behavior when
creating the function and class index pages. This is now fixed, closing
issue 2048_. Thanks to Daniel Diniz for help diagnosing the problem.Most warnings and a few errors now have links to a page in the docs
explaining the specific message. Closes
issue 1921_... _issue 1921: #1921
.. _issue 2048: #2048
.. _changes_7-10-6:
v7.10.6Compare Source
Fix:
sourcedirectories were not properly communicated to subprocessesthat ran in different directories, as reported in
issue 1499_. This is nowfixed.
Performance:
Alex Gaynor continues fine-tuning <pull 2038_>_ the speed ofcombination, especially with many contexts.
.. _issue 1499: #1499
.. _pull 2038: #2038
.. _changes_7-10-5:
v7.10.5Compare Source
coverage combine: it's now about twice asfast! Huge thanks to Alex Gaynor for pull requests
2032 <pull 2032_>,2033 <pull 2033_>, and2034 <pull 2034_>_... _pull 2032: #2032
.. _pull 2033: #2033
.. _pull 2034: #2034
.. _changes_7-10-4:
v7.10.4Compare Source
Added
patch = forkfor times when the built-in forking support isinsufficient.
Fix:
patch = execvalso inherits the entire coverage configuration now... _changes_7-10-3:
v7.10.3Compare 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
ModuleNotFounderror 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 runcommand line (such as--branch) wouldn't be communicated to the subprocesses. This couldlead to combining failures, as described in
issue 2021_. Now the entireconfiguration is used in subprocesses, regardless of its origin.
Added
debug=patchto 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.2Compare Source
actually executed. This is now fixed, closing
issue 1999_. Python 3.9still shows the problem.
.. _issue 1999: #1999
.. _changes_7-10-1:
v7.10.1Compare Source
Fix: the exclusion for
if TYPE_CHECKING:was wrong: it marked the branchas 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, closingissue 2006_... _issue 2006: #2006
.. _changes_7-10-0:
v7.10.0Compare Source
A new configuration option: ":ref:
config_run_patch" specifies named patchesto work around some limitations in coverage measurement. These patches are
available:
patch = _exitlets coverage save its data even when :func:os._exit() <python:os._exit>is used to abruptly end the process. This closeslong-standing
issue 310_ as well as its duplicates:issue 312,issue 1673,issue 1845, andissue 1941.patch = subprocessmeasures coverage in Python subprocesses createdwith :mod:
subprocess, :func:os.system, or one of the :func:execv <python:os.execl>or :func:spawnv <python:os.spawnl>family offunctions. Closes old
issue 367, its duplicateissue 378and oldissue 689_.patch = execvadjusts the :func:execv <python:os.execl>family offunctions to save coverage data before ending the current program and
starting the next. Not available on Windows. Closes
issue 43_ after 15years!
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 automaticallyexcluded as a line and
if TYPE_CHECKING:is excluded as a branch. Closesissue 831_.A new command-line option:
--save-signal=USR1specifies a signal thatcoverage.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 ofregexes to add as pragmas for partial branches. This parallels the
":ref:
config_report_exclude_also" setting for adding line exclusionpatterns.
A few file path configuration settings didn't allow for tilde expansion:
:ref:
config_json_output, :ref:config_lcov_outputand: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.2Compare 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.1Compare 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.0Compare Source
Added a
[run] coreconfiguration 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, closingissue 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.2Compare Source
Thanks,
Finn Womack <pull 1972_>_... _issue 1971: #1971
.. _pull 1972: #1972
.. _changes_7-8-1:
v7.8.1Compare 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:
v7.8.0Compare Source
Added a new
source_dirssetting for symmetry with the existingsource_pkgssetting. It's preferable to the existingsourcesetting,because you'll get a clear error when directories don't exist. Fixes
issue 1942. Thanks,Jeremy Fleischman <pull 1943_>.Fix: the PYTHONSAFEPATH environment variable new in Python 3.11 is properly
supported, closing
issue 1696. Thanks,Philipp A. <pull 1700_>. Thisworks properly except for a detail when using the
coveragecommand onWindows. There you can use
python -m coverageinstead if you need exactemulation.
.. _issue 1696: #1696
.. _pull 1700: #1700
.. _issue 1942: #1942
.. _pull 1943: #1943
.. _changes_7-7-1:
v7.7.1Compare Source
test!
.. _changes_7-7-0:
v7.7.0Compare Source
The Coverage object has a new method, :meth:
.Coverage.branch_statsforgetting simple branch information for a module. Closes
issue 1888_.The :class:
Coverage constructor<.Coverage>now has apluginsparameterfor passing in plugin objects directly, thanks to
Alex Gaynor <pull 1919_>_.Many constant tests in if statements are now recognized as being optimized
away. For example, previously
if 13:would have been considered a branchwith one path not taken. Now it is understood as always true and no coverage
is missing.
The experimental sys.monitoring support now works for branch coverage if you
are using Python 3.14.0 alpha 6 or newer. This should reduce the overhead
coverage.py imposes on your test suite. Set the environment variable
COVERAGE_CORE=sysmonto try it out.Confirmed support for PyPy 3.11. Thanks Michał Górny.
.. _issue 1888: #1888
.. _pull 1919: #1919
.. _changes_7-6-12:
v7.6.12Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927: #1927
.. _changes_7-6-11:
v7.6.11Compare Source
Fix: a memory leak in CTracer has been fixed. The details are in
issue 1924_ andpytest-dev 676_. This should reduce the memory footprint foreveryone even if it hadn't caused a problem before.
We now ship a py3-none-any.whl wheel file. Thanks,
Russell Keith-Magee <pull 1914_>_... _pull 1914: #1914
.. _issue 1924: #1924
.. _pytest-dev 676: pytest-dev/pytest-cov#676
.. _changes_7-6-10:
v7.6.10Compare Source
Fix: some descriptions of missing branches in HTML and LCOV reports were
incorrect when multi-line statements were involved (
issue 1874_ andissue 1875_). These are now fixed.Fix: Python 3.14
defers evaluation of annotations <pep649_>_ by moving theminto separate code objects. That code is rarely executed, so coverage.py
would mark them as missing, as reported in
issue 1908_. Now they areignored 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'tunderstand the problem or the solution, but
git bisecthelped find it,and now it's fixed.
Docs: re-wrote the :ref:
subprocesspage to put multiprocessing first and tohighlight the correct use of :class:
multiprocessing.Pool <python:multiprocessing.pool.Pool>... _issue 1874: #1874
.. _issue 1875: #1875
.. _issue 1902: #1902
.. _issue 1908: #1908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-deferred-annotations
.. _changes_7-6-9:
v7.6.9Compare Source
Tomas Uribe fixed <pull 1901_>_ a performance problem in the XMLreport. Large code bases should produce XML reports much faster now.
.. _pull 1901: #1901
.. _changes_7-6-8:
v7.6.8Compare Source
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: #1896
.. _changes_7-6-7:
v7.6.7Compare Source
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6Compare Source
reported in
issue 1891_. The assert has been removed... _issue 1891: #1891
.. _changes_7-6-5:
v7.6.5Compare Source
Fix: fine-tuned the exact Python version (3.12.6) when exiting from
withstatements changed how they traced. This affected whether people saw the
fix for
issue 1880_.Fix: isolate our code more from mocking in the os module that in rare cases
can cause
bizarre behavior <pytest-cov-666_>_.Refactor: some code unreachable code paths in parser.py were changed to
asserts. If you encounter any of these, please let me know!
.. _pytest-cov-666: pytest-dev/pytest-cov#666
.. _changes_7-6-4:
v7.6.4Compare Source
withstatements could cause contained branches to beincorrectly marked as missing (
issue 1880_). This is now fixed... _issue 1880: #1880
.. _changes_7-6-3:
v7.6.3Compare Source
Fix: nested context managers could incorrectly be analyzed to flag a missing
branch on the last context manager, as described in
issue 1876_. This isnow fixed.
Fix: the missing branch message about not exiting a module had an extra
"didn't," as described in
issue 1873_. This is now fixed... _issue 1873: #1873
.. _issue 1876: #1876
.. _changes_7-6-2:
v7.6.2Compare Source
Dropped support for Python 3.8 and PyPy 3.8.
Fix: a final wildcard match/case clause assigning to a name (
case _ as value) was incorrectly marked as a missing branch. This is now fixed,closing
issue 1860_.Fewer things are considered branches now. Lambdas, comprehensions, and
generator expressions are no longer marked as missing branches if they don't
complete execution. Closes
issue 1852_.Fix: the HTML report didn't properly show multi-line f-strings that end with
a backslash continuation. This is now fixed, closing
issue 1836, thanksto
LiuYinCarl and Marco Ricci <pull 1838_>.Fix: the LCOV report now has correct line numbers (fixing
issue 1846) andbetter branch descriptions for BRDA records (fixing
issue 1850). Thereare other changes to lcov also, including a new configuration option
:ref:
line_checksums <config_lcov_line_checksums>to control whether linechecksums are included in the lcov report. The default is false. To keep
checksums set it to true. All this work is thanks to Zack Weinberg
(
pull 1849_ andpull 1851_).Fixed the docs for multi-line regex exclusions, closing
issue 1863_.Fixed a potential crash in the C tracer, closing
issue 1835, thanks toJan Kühle <pull 1843_>... _issue 1835: #1835
.. _issue 1836: #1836
.. _pull 1838: #1838
.. _pull 1843: #1843
.. _issue 1846: #1846
.. _pull 1849: #1849
.. _issue 1850: #1850
.. _pull 1851: #1851
.. _issue 1852: #1852
.. _issue 1860: #1860
.. _issue 1863: #1863
.. _changes_7-6-1:
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.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).