chore(deps): update dependency coverage to v7 #157

renovate · 2024-06-13T19:40:33Z

This PR contains the following updates:

Package	Change	Age	Confidence
coverage	`^6.1.2` -> `^7.0.0`

Release Notes

nedbat/coveragepy (coverage)

`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:https://github.com/nedbat/coveragepy/issues/19999

.. _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:https://github.com/nedbat/coveragepy/issues/20066

.. _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_ and duplicate issue 378_.
- 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_.

.. _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:https://github.com/nedbat/coveragepy/pull/19844
.. _issue 1991https://github.com/nedbat/coveragepy/issues/199191

.. _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:https://github.com/nedbat/coveragepy/issues/17466
.. _issue 1977https://github.com/nedbat/coveragepy/issues/197777
.. _pull 197https://github.com/nedbat/coveragepy/pull/1978978
.. _issue 19https://github.com/nedbat/coveragepy/issues/19801980
.. _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:https://github.com/nedbat/coveragepy/pull/19711
.. _pull 1972https://github.com/nedbat/coveragepy/pull/197272

.. _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:https://github.com/nedbat/coveragepy/issues/19666
.. _pull 1967https://github.com/nedbat/coveragepy/pull/196767
.. _issue 197https://github.com/nedbat/coveragepy/issues/1970970

.. _changes_7-8-0:

`v7.8.0`

Compare Source

Added a new source_dirs setting for symmetry with the existing
source_pkgs setting. It's preferable to the existing source setting,
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_>. This
works properly except for a detail when using the coverage command on
Windows. There you can use python -m coverage instead if you need exact
emulation.

.. _issue 1696:https://github.com/nedbat/coveragepy/issues/16966
.. _pull 1700https://github.com/nedbat/coveragepy/pull/170000
.. _issue 194https://github.com/nedbat/coveragepy/issues/1942942
.. _pull 19https://github.com/nedbat/coveragepy/pull/19431943

.. _changes_7-7-1:

`v7.7.1`

Compare Source

A few small tweaks to the sys.monitoring support for Python 3.14. Please
test!

.. _changes_7-7-0:

`v7.7.0`

Compare Source

The Coverage object has a new method, :meth:.Coverage.branch_stats for
getting simple branch information for a module. Closes issue 1888_.
The :class:Coverage constructor<.Coverage> now has a plugins parameter
for 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 branch
with 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=sysmon to try it out.
Confirmed support for PyPy 3.11. Thanks Michał Górny.

.. _issue 1888:https://github.com/nedbat/coveragepy/issues/18888
.. _pull 1919https://github.com/nedbat/coveragepy/pull/191919

.. _changes_7-6-12:

`v7.6.12`

Compare Source

Fix: some aarch64 distributions were missing (issue 1927_). These are now
building reliably.

.. _issue 1927:https://github.com/nedbat/coveragepy/issues/19277

.. _changes_7-6-11:

`v7.6.11`

Compare Source

Fix: a memory leak in CTracer has been fixed. The details are in issue 1924_ and pytest-dev 676_. This should reduce the memory footprint for
everyone 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:https://github.com/nedbat/coveragepy/pull/19144
.. _issue 1924https://github.com/nedbat/coveragepy/issues/192424
.. _pytest-dev 67https://github.com/pytest-dev/pytest-cov/issues/676676

.. _changes_7-6-10:

`v7.6.10`

Compare Source

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/18744
.. _issue 1875https://github.com/nedbat/coveragepy/issues/187575
.. _issue 190https://github.com/nedbat/coveragepy/issues/1902902
.. _issue 19https://github.com/nedbat/coveragepy/issues/19081908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#whatsnew314-pep649

.. _changes_7-6-9:

`v7.6.9`

Compare Source

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/19011

.. _changes_7-6-8:

`v7.6.8`

Compare 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:https://github.com/nedbat/coveragepy/issues/18966

.. _changes_7-6-7:

`v7.6.7`

Compare Source

Fix: ugh, the other assert from 7.6.5 can also be encountered in the wild,
so it's been restored to a conditional. Sorry for the churn.

.. _changes_7-6-6:

`v7.6.6`

Compare Source

One of the new asserts from 7.6.5 caused problems in real projects, as
reported in issue 1891_. The assert has been removed.

.. _issue 1891:https://github.com/nedbat/coveragepy/issues/18911

.. _changes_7-6-5:

`v7.6.5`

Compare Source

Fix: fine-tuned the exact Python version (3.12.6) when exiting from with
statements 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:https://github.com/pytest-dev/pytest-cov/issues/6666

.. _changes_7-6-4:

`v7.6.4`

Compare Source

Fix: multi-line with statements could cause contained branches to be
incorrectly marked as missing (issue 1880_). This is now fixed.

.. _issue 1880:https://github.com/nedbat/coveragepy/issues/18800

.. _changes_7-6-3:

`v7.6.3`

Compare 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 is
now 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:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676

.. _changes_7-6-2:

`v7.6.2`

Compare 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, thanks
to LiuYinCarl and Marco Ricci <pull 1838_>.
Fix: the LCOV report now has correct line numbers (fixing issue 1846) and
better branch descriptions for BRDA records (fixing issue 1850). There
are other changes to lcov also, including a new configuration option
:ref:line_checksums <config_lcov_line_checksums> to control whether line
checksums 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_ and pull 1851_).
Fixed the docs for multi-line regex exclusions, closing issue 1863_.
Fixed a potential crash in the C tracer, closing issue 1835, thanks to
Jan Kühle <pull 1843_>.

.. _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863

.. _changes_7-6-1:

`v7.6.1`

Compare Source

Fix: some aarch64 distributions were missing (issue 1927_). These are now
building reliably.

.. _issue 1927:https://github.com/nedbat/coveragepy/issues/19277

.. _changes_7-6-11:

`v7.6.0`

Compare Source

Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those
requested in issues 118 <issue 118_> (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_
(arbitrary sequence of marked lines). See the :ref:multi_line_exclude
section of the docs for more details and examples.
The JSON report now includes per-function and per-class coverage information.
Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This
closes issue 1793_ and issue 1532_.
Fixed an incorrect calculation of "(no class)" lines in the HTML classes
report.
Python 3.13.0b3 is supported.

.. _changes_7-5-4:

`v7.5.4`

Compare Source

If you attempt to combine statement coverage data with branch coverage data,
coverage.py used to fail with the message "Can't combine arc data with line
data" or its reverse, "Can't combine line data with arc data." These
messages used internal terminology, making it hard for people to understand
the problem. They are now changed to mention "branch coverage data" and
"statement coverage data."
Fixed a minor branch coverage problem with wildcard match/case cases using
names or guard clauses.
Started testing on 3.13 free-threading (nogil) builds of Python. I'm not
claiming full support yet. Closes issue 1799_.

.. _issue 1799:https://github.com/nedbat/coveragepy/issues/17999

.. _changes_7-5-3:

`v7.5.3`

Compare Source

Performance improvements for combining data files, especially when measuring
line coverage. A few different quadratic behaviors were eliminated. In one
extreme case of combining 700+ data files, the time dropped from more than
three hours to seven minutes. Thanks for Kraken Tech for funding the fix.
Performance improvements for generating HTML reports, with a side benefit of
reducing memory use, closing issue 1791_. Thanks to Daniel Diniz for
helping to diagnose the problem.

.. _issue 1791:https://github.com/nedbat/coveragepy/issues/17911

.. _changes_7-5-2:

`v7.5.2`

Compare Source

Fix: nested matches of exclude patterns could exclude too much code, as
reported in issue 1779_. This is now fixed.
Changed: previously, coverage.py would consider a module docstring to be an
executable statement if it appeared after line 1 in the file, but not
executable if it was the first line. Now module docstrings are never counted
as executable statements. This can change coverage.py's count of the number
of statements in a file, which can slightly change the coverage percentage
reported.
In the HTML report, the filter term and "hide covered" checkbox settings are
remembered between viewings, thanks to Daniel Diniz <pull 1776_>_.
Python 3.13.0b1 is supported.
Fix: parsing error handling is improved to ensure bizarre source files are
handled gracefully, and to unblock oss-fuzz fuzzing, thanks to Liam DeVoe <pull 1788_>. Closes issue 1787.

.. _pull 1776:https://github.com/nedbat/coveragepy/pull/17766
.. _issue 1779https://github.com/nedbat/coveragepy/issues/177979
.. _issue 178https://github.com/nedbat/coveragepy/issues/1787787
.. _pull 17https://github.com/nedbat/coveragepy/pull/17881788

.. _changes_7-5-1:

`v7.5.1`

Compare Source

Fix: a pragma comment on the continuation lines of a multi-line statement
now excludes the statement and its body, the same as if the pragma is
on the first line. This closes issue 754. The fix was contributed by
Daniel Diniz <pull 1773_>.
Fix: very complex source files like this one <resolvent_lookup_>_ could
cause a maximum recursion error when creating an HTML report. This is now
fixed, closing issue 1774_.
HTML report improvements:
- Support files (JavaScript and CSS) referenced by the HTML report now have
  hashes added to their names to ensure updated files are used instead of
  stale cached copies.
- Missing branch coverage explanations that said "the condition was never
  false" now read "the condition was always true" because it's easier to
  understand.
- Column sort order is remembered better as you move between the index pages,
  fixing issue 1766. Thanks, Daniel Diniz <pull 1768_>.

.. _resolvent_lookup: https://github.com/sympy/sympy/blob/130950f3e6b3f97fcc17f4599ac08f70fdd2e9d4/sympy/polys/numberfields/resolvent\_lookup.py
.. _issue 7https://github.com/nedbat/coveragepy/issues/754/754
.. _issue 1https://github.com/nedbat/coveragepy/issues/1766/1766
.. _pull https://github.com/nedbat/coveragepy/pull/1768l/1768
.. _pullhttps://github.com/nedbat/coveragepy/pull/1773ll/1773
.. _issuhttps://github.com/nedbat/coveragepy/issues/1774ues/1774

.. _changes_7-5-0:

`v7.5.0`

Compare Source

Added initial support for function and class reporting in the HTML report.
There are now three index pages which link to each other: files, functions,
and classes. Other reports don't yet have this information, but it will be
added in the future where it makes sense. Feedback gladly accepted!
Finishes issue 780_.
Other HTML report improvements:
- There is now a "hide covered" checkbox to filter out 100% files, finishing
  issue 1384_.
- The index page is always sorted by one of its columns, with clearer
  indications of the sorting.
- The "previous file" shortcut key didn't work on the index page, but now it
  does, fixing issue 1765_.
The debug output showing which configuration files were tried now shows
absolute paths to help diagnose problems where settings aren't taking effect,
and is renamed from "attempted_config_files" to the more logical
"config_files_attempted."
Python 3.13.0a6 is supported.

.. _issue 780:https://github.com/nedbat/coveragepy/issues/7800
.. _issue 1384https://github.com/nedbat/coveragepy/issues/138484
.. _issue 176https://github.com/nedbat/coveragepy/issues/1765765

.. _changes_7-4-4:

`v7.4.4`

Compare Source

Fix: in some cases, even with [run] relative_files=True, a data file
could be created with absolute path names. When combined with other relative
data files, it was random whether the absolute file names would be made
relative or not. If they weren't, then a file would be listed twice in
reports, as detailed in issue 1752_. This is now fixed: absolute file
names are always made relative when combining. Thanks to Bruno Rodrigues dos
Santos for support.
Fix: the last case of a match/case statement had an incorrect message if the
branch was missed. It said the pattern never matched, when actually the
branch is missed if the last case always matched.
Fix: clicking a line number in the HTML report now positions more accurately.
Fix: the report:format setting was defined as a boolean, but should be a
string. Thanks, Tanaydin Sirin <pull 1754_>_. It is also now documented
on the :ref:configuration page <config_report_format>.

.. _issue 1752:https://github.com/nedbat/coveragepy/issues/17522
.. _pull 1754https://github.com/nedbat/coveragepy/pull/175454

.. _changes_7-4-3:

`v7.4.3`

Compare Source

Fix: in some cases, coverage could fail with a RuntimeError: "Set changed
size during iteration." This is now fixed, closing issue 1733_.

.. _issue 1733:https://github.com/nedbat/coveragepy/issues/17333

.. _changes_7-4-2:

`v7.4.2`

Compare Source

Fix: setting COVERAGE_CORE=sysmon no longer errors on 3.11 and lower,
thanks Hugo van Kemenade <pull 1747_>_. It now issues a warning that
sys.monitoring is not available and falls back to the default core instead.

.. _pull 1747:https://github.com/nedbat/coveragepy/pull/17477

.. _changes_7-4-1:

`v7.4.1`

Compare Source

Python 3.13.0a3 is supported.
Fix: the JSON report now includes an explicit format version number, closing
issue 1732_.

.. _issue 1732:https://github.com/nedbat/coveragepy/issues/17322

.. _changes_7-4-0:

`v7.4.0`

Compare Source

In Python 3.12 and above, you can try an experimental core based on the new
:mod:sys.monitoring <python:sys.monitoring> module by defining a
COVERAGE_CORE=sysmon environment variable. This should be faster for
line coverage, but not for branch coverage, and plugins and dynamic contexts
are not yet supported with it. I am very interested to hear how it works (or
doesn't!) for you.

.. _changes_7-3-4:

`v7.3.4`

Compare Source

Fix: the change for multi-line signature exclusions in 7.3.3 broke other
forms of nested clauses being excluded properly. This is now fixed, closing
issue 1713_.
Fix: in the HTML report, selecting code for copying won't select the line
numbers also. Thanks, Robert Harris <pull 1717_>_.

.. _issue 1713:https://github.com/nedbat/coveragepy/issues/17133
.. _pull 1717https://github.com/nedbat/coveragepy/pull/171717

.. _changes_7-3-3:

`v7.3.3`

Compare Source

Fix: function definitions with multi-line signatures can now be excluded by
matching any of the lines, closing issue 684. Thanks, Jan Rusak, Maciej Kowalczyk and Joanna Ejzel <pull 1705_>.
Fix: XML reports could fail with a TypeError if files had numeric components
that were duplicates except for leading zeroes, like file1.py and
file001.py. Fixes issue 1709_.
The coverage annotate command used to announce that it would be removed
in a future version. Enough people got in touch to say that they use it, so
it will stay. Don't expect it to keep up with other new features though.
Added new :ref:debug options <cmd_run_debug>:
- pytest writes the pytest test name into the debug output.
- dataop2 writes the full data being added to CoverageData objects.

.. _issue 684:https://github.com/nedbat/coveragepy/issues/6844
.. _pull 1705https://github.com/nedbat/coveragepy/pull/170505
.. _issue 170https://github.com/nedbat/coveragepy/issues/1709709

.. _changes_7-3-2:

`v7.3.2`

Compare Source

The coverage lcov command ignored the [report] exclude_lines and
[report] exclude_also settings (issue 1684). This is now fixed,
thanks Jacqueline Lee <pull 1685_>.
Sometimes SQLite will create journal files alongside the coverage.py database
files. These are ephemeral, but could be mistakenly included when combining
data files. Now they are always ignored, fixing issue 1605_. Thanks to
Brad Smith for suggesting fixes and providing detailed debugging.
On Python 3.12+, we now disable SQLite writing journal files, which should be
a little faster.
The new 3.12 soft keyword type is properly bolded in HTML reports.
Removed the "fullcoverage" feature used by CPython to measure the coverage of
early-imported standard library modules. CPython stopped using it <88054_>_ in 2021, and it stopped working completely in Python 3.13.

.. _issue 1605:https://github.com/nedbat/coveragepy/issues/16055
.. _issue 1684https://github.com/nedbat/coveragepy/issues/168484
.. _pull 168https://github.com/nedbat/coveragepy/pull/1685685
.. _880https://github.com/python/cpython/issues/880548054

.. _changes_7-3-1:

`v7.3.1`

Compare Source

The semantics of stars in file patterns has been clarified in the docs. A
leading or trailing star matches any number of path components, like a double
star would. This is different than the behavior of a star in the middle of a
pattern. This discrepancy was identified by Sviatoslav Sydorenko <starbad_>, who provided patient detailed diagnosis <pull 1650_> and
graciously agreed to a pragmatic resolution.
The API docs were missing from the last version. They are now restored <apidocs_>_.

.. _apidocs: https://coverage.readthedocs.io/en/latest/api\_coverage.html
.. _starbahttps://github.com/nedbat/coveragepy/issues/1407#issuecomment-1631085209209
.. _pull 16https://github.com/nedbat/coveragepy/pull/16501650

.. _changes_7-3-0:

`v7.3.0`

Compare Source

Added a :meth:.Coverage.collect context manager to start and stop coverage
data collection.
Dropped support for Python 3.7.
Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode.
Coverage.py would fail with the error Safety level may not be changed inside a transaction. This is now avoided, closing issue 1646_. Thanks
to Michael Bell for the detailed bug report.
Docs: examples of configuration files now include separate examples for the
different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.
Fix: added nosemgrep comments to our JavaScript code so that
semgrep-based SAST security checks won't raise false alarms about security
problems that aren't problems.
Added a CITATION.cff file, thanks to Ken Schackart <pull 1641_>_.

.. _pull 1641:https://github.com/nedbat/coveragepy/pull/16411
.. _issue 1646https://github.com/nedbat/coveragepy/issues/164646

.. _changes_7-2-7:

`v7.2.7`

Compare Source

Fix: reverted a change from 6.4.3 <pull 1347b_>_ that helped Cython, but
also increased the size of data files when using dynamic contexts, as
described in the now-fixed issue 1586. The problem is now avoided due to a
recent change (issue 1538 <issue 1538b_>). Thanks to Anders Kaseorg <pull 1629_>_ and David Szotten for persisting with problem reports and
detailed diagnoses.
Wheels are now provided for CPython 3.12.

.. _pull 1347b:https://github.com/nedbat/coveragepy/pull/13477
.. _issue 1538bhttps://github.com/nedbat/coveragepy/issues/153838
.. _issue 158https://github.com/nedbat/coveragepy/issues/1586586
.. _pull 16https://github.com/nedbat/coveragepy/pull/16291629

.. _changes_7-2-6:

`v7.2.6`

Compare Source

Fix: the lcov command could raise an IndexError exception if a file is
translated to Python but then executed under its own name. Jinja2 does this
when rendering templates. Fixes issue 1553_.
Python 3.12 beta 1 now inlines comprehensions. Previously they were compiled
as invisible functions and coverage.py would warn you if they weren't
completely executed. This no longer happens under Python 3.12.
Fix: the coverage debug sys command includes some environment variables
in its output. This could have included sensitive data. Those values are
now hidden with asterisks, closing issue 1628_.

.. _issue 1553:https://github.com/nedbat/coveragepy/issues/15533
.. _issue 1628https://github.com/nedbat/coveragepy/issues/162828

.. _changes_7-2-5:

`v7.2.5`

Compare Source

Fix: html_report() could fail with an AttributeError on isatty if run
in an unusual environment where sys.stdout had been replaced. This is now
fixed.

.. _changes_7-2-4:

`v7.2.4`

Compare Source

PyCon 2023 sprint fixes!

Fix: with relative_files = true, specifying a specific file to include or
omit wouldn't work correctly (issue 1604). This is now fixed, with
testing help by Marc Gibbons <pull 1608_>.
Fix: the XML report would have an incorrect <source> element when using
relative files and the source option ended with a slash (issue 1541).
This is now fixed, thanks to Kevin Brown-Silva <pull 1608_>.
When the HTML report location is printed to the terminal, it's now a
terminal-compatible URL, so that you can click the location to open the HTML
file in your browser. Finishes issue 1523_ thanks to Ricardo Newbery <pull 1613_>_.
Docs: a new :ref:Migrating page <migrating> with details about how to
migrate between major versions of coverage.py. It currently covers the
wildcard changes in 7.x. Thanks, Brian Grohe <pull 1610_>_.

.. _issue 1523:https://github.com/nedbat/coveragepy/issues/15233
.. _issue 1541https://github.com/nedbat/coveragepy/issues/154141
.. _issue 160https://github.com/nedbat/coveragepy/issues/1604604
.. _pull 16https://github.com/nedbat/coveragepy/pull/16081608
.. _pull 1https://github.com/nedbat/coveragepy/pull/1609/1609
.. _pull https://github.com/nedbat/coveragepy/pull/1610l/1610
.. _pullhttps://github.com/nedbat/coveragepy/pull/1613ll/1613

.. _changes_7-2-3:

`v7.2.3`

Compare Source

Fix: the :ref:config_run_sigterm setting was meant to capture data if a
process was terminated with a SIGTERM signal, but it didn't always. This was
fixed thanks to Lewis Gaul <pull 1600_>, closing issue 1599.
Performance: HTML reports with context information are now much more compact.
File sizes are typically as small as one-third the previous size, but can be
dramatically smaller. This closes issue 1584_ thanks to Oleh Krehel <pull 1587_>_.
Development dependencies no longer use hashed pins, closing issue 1592_.

.. _issue 1584:https://github.com/nedbat/coveragepy/issues/15844
.. _pull 1587https://github.com/nedbat/coveragepy/pull/158787
.. _issue 159https://github.com/nedbat/coveragepy/issues/1592592
.. _issue 15https://github.com/nedbat/coveragepy/issues/15991599
.. _pull 1https://github.com/nedbat/coveragepy/pull/1600/1600

.. _changes_7-2-2:

`v7.2.2`

Compare Source

Fix: if a virtualenv was created inside a source directory, and a sourced
package was installed inside the virtualenv, then all of the third-party
packages inside the virtualenv would be measured. This was incorrect, but
has now been fixed: only the specified packages will be measured, thanks to
Manuel Jacob <pull 1560_>_.
Fix: the coverage lcov command could create a .lcov file with incorrect
LF (lines found) and LH (lines hit) totals. This is now fixed, thanks to
Ian Moore <pull 1583_>_.
Fix: the coverage xml command on Windows could create a .xml file with
duplicate <package> elements. This is now fixed, thanks to Benjamin Parzella <pull 1574_>, closing issue 1573.

.. _pull 1560:https://github.com/nedbat/coveragepy/pull/15600
.. _issue 1573https://github.com/nedbat/coveragepy/issues/157373
.. _pull 157https://github.com/nedbat/coveragepy/pull/1574574
.. _pull 15https://github.com/nedbat/coveragepy/pull/15831583

.. _changes_7-2-1:

`v7.2.1`

Compare Source

Fix: the PyPI page had broken links to documentation pages, but no longer
does, closing issue 1566_.
Fix: public members of the coverage module are now properly indicated so that
mypy will find them, fixing issue 1564_.

.. _issue 1564:https://github.com/nedbat/coveragepy/issues/15644
.. _issue 1566https://github.com/nedbat/coveragepy/issues/156666

.. _changes_7-2-0:

`v7.2.0`

Compare Source

Added a new setting [report] exclude_also to let you add more exclusions
without overwriting the defaults. Thanks, Alpha Chen <pull 1557_>,
closing issue 1391.
Added a :meth:.CoverageData.purge_files method to remove recorded data for
a particular file. Contributed by Stephan Deibel <pull 1547_>_.
Fix: when reporting commands fail, they will no longer congratulate
themselves with messages like "Wrote XML report to file.xml" before spewing a
traceback about their failure.
Fix: arguments in the public API that name file paths now accept pathlib.Path
objects. This includes the data_file and config_file arguments to
the Coverage constructor and the basename argument to CoverageData.
Closes issue 1552_.
Fix: In some embedded environments, an IndexError could occur on stop() when
the originating thread exits before completion. This is now fixed, thanks to
Russell Keith-Magee <pull 1543_>, closing issue 1542.
Added a py.typed file to announce our type-hintedness. Thanks,
KotlinIsland <pull 1550_>_.

.. _issue 1391:https://github.com/nedbat/coveragepy/issues/13911
.. _issue 1542https://github.com/nedbat/coveragepy/issues/154242
.. _pull 154https://github.com/nedbat/coveragepy/pull/1543543
.. _pull 15https://github.com/nedbat/coveragepy/pull/15471547
.. _pull 1https://github.com/nedbat/coveragepy/pull/1550/1550
.. _issue https://github.com/nedbat/coveragepy/issues/1552s/1552
.. _pullhttps://github.com/nedbat/coveragepy/pull/1557ll/1557

.. _changes_7-1-0:

`v7.1.0`

Compare Source

Added: the debug output file can now be specified with [run] debug_file
in the configuration file. Closes issue 1319_.
Performance: fixed a slowdown with dynamic contexts that's been around since
6.4.3. The fix closes issue 1538. Thankfully this doesn't break the
Cython change that fixed issue 972_. Thanks to Mathieu Kniewallner for
the deep investigative work and comprehensive issue report.
Typing: all product and test code has type annotations.

.. _Cython change:https://github.com/nedbat/coveragepy/pull/13477
.. _issue 972https://github.com/nedbat/coveragepy/issues/97272
.. _issue 131https://github.com/nedbat/coveragepy/issues/1319319
.. _issue 15https://github.com/nedbat/coveragepy/issues/15381538

.. _changes_7-0-5:

`v7.0.5`

Compare Source

Fix: On Python 3.7, a file with type annotations but no from __future__ import annotations would be missing statements in the coverage report. This
is now fixed, closing issue 1524_.

.. _issue 1524:https://github.com/nedbat/coveragepy/issues/15244

.. _changes_7-0-4:

`v7.0.4`

Compare Source

Performance: an internal cache of file names was accidentally disabled,
resulting in sometimes drastic reductions in performance. This is now fixed,
closing issue 1527_. Thanks to Ivan Ciuvalschii for the reproducible test
case.

.. _issue 1527:https://github.com/nedbat/coveragepy/issues/15277

.. _changes_7-0-3:

`v7.0.3`

Compare Source

Fix: when using pytest-cov or pytest-xdist, or perhaps both, the combining
step could fail with assert row is not None using 7.0.2. This was due to
a race condition that has always been possible and is still possible. In
7.0.1 and before, the error was silently swallowed by the combining code.
Now it will produce a message "Couldn't combine data file" and ignore the
data file as it used to do before 7.0.2. Closes issue 1522_.

.. _issue 1522:https://github.com/nedbat/coveragepy/issues/15222

.. _changes_7-0-2:

`v7.0.2`

Compare Source

Fix: when using the [run] relative_files = True setting, a relative
[paths] pattern was still being made absolute. This is now fixed,
closing issue 1519_.
Fix: if Python doesn't provide tomllib, then TOML configuration files can
only be read if coverage.py is installed with the [toml] extra.
Coverage.py will raise an error if TOML support is not installed when it sees
your settings are in a .toml file. But it didn't understand that
[tools.coverage] was a valid section header, so the error wasn't reported
if you used that header, and settings were silently ignored. This is now
fixed, closing issue 1516_.
Fix: adjusted how decorators are traced on PyPy 7.3.10, fixing issue 1515_.
Fix: the coverage lcov report did not properly implement the
--fail-under=MIN option. Thi

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 · 2024-06-13T19:40:34Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock

Updating dependencies
Resolving dependencies...

The "poetry.dev-dependencies" section is deprecated and will be removed in a future version. Use "poetry.group.dev.dependencies" instead.

The current project's supported Python range (>=3.6.2,<3.7) is not compatible with some of the required packages Python requirement:
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.7, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.8, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7
  - coverage requires Python >=3.9, so it will not be installable for Python >=3.6.2,<3.7

Because no versions of coverage match >7.0.0,<7.0.1 || >7.0.1,<7.0.2 || >7.0.2,<7.0.3 || >7.0.3,<7.0.4 || >7.0.4,<7.0.5 || >7.0.5,<7.1.0 || >7.1.0,<7.2.0 || >7.2.0,<7.2.1 || >7.2.1,<7.2.2 || >7.2.2,<7.2.3 || >7.2.3,<7.2.4 || >7.2.4,<7.2.5 || >7.2.5,<7.2.6 || >7.2.6,<7.2.7 || >7.2.7,<7.3.0 || >7.3.0,<7.3.1 || >7.3.1,<7.3.2 || >7.3.2,<7.3.3 || >7.3.3,<7.3.4 || >7.3.4,<7.4.0 || >7.4.0,<7.4.1 || >7.4.1,<7.4.2 || >7.4.2,<7.4.3 || >7.4.3,<7.4.4 || >7.4.4,<7.5.0 || >7.5.0,<7.5.1 || >7.5.1,<7.5.2 || >7.5.2,<7.5.3 || >7.5.3,<7.5.4 || >7.5.4,<7.6.0 || >7.6.0,<7.6.1 || >7.6.1,<7.6.2 || >7.6.2,<7.6.3 || >7.6.3,<7.6.4 || >7.6.4,<7.6.5 || >7.6.5,<7.6.6 || >7.6.6,<7.6.7 || >7.6.7,<7.6.8 || >7.6.8,<7.6.9 || >7.6.9,<7.6.10 || >7.6.10,<7.6.11 || >7.6.11,<7.6.12 || >7.6.12,<7.7.0 || >7.7.0,<7.7.1 || >7.7.1,<7.8.0 || >7.8.0,<7.8.1 || >7.8.1,<7.8.2 || >7.8.2,<7.9.0 || >7.9.0,<7.9.1 || >7.9.1,<7.9.2 || >7.9.2,<7.10.0 || >7.10.0,<7.10.1 || >7.10.1,<7.10.2 || >7.10.2,<8.0.0
 and coverage (7.0.0) requires Python >=3.7, coverage is forbidden.
And because coverage (7.0.1) requires Python >=3.7
 and coverage (7.0.2) requires Python >=3.7, coverage is forbidden.
And because coverage (7.0.3) requires Python >=3.7
 and coverage (7.0.4) requires Python >=3.7, coverage is forbidden.
And because coverage (7.0.5) requires Python >=3.7
 and coverage (7.1.0) requires Python >=3.7, coverage is forbidden.
And because coverage (7.2.0) requires Python >=3.7
 and coverage (7.2.1) requires Python >=3.7, coverage is forbidden.
And because coverage (7.2.2) requires Python >=3.7
 and coverage (7.2.3) requires Python >=3.7, coverage is forbidden.
And because coverage (7.2.4) requires Python >=3.7
 and coverage (7.2.5) requires Python >=3.7, coverage is forbidden.
And because coverage (7.2.6) requires Python >=3.7
 and coverage (7.2.7) requires Python >=3.7, coverage is forbidden.
And because coverage (7.3.0) requires Python >=3.8
 and coverage (7.3.1) requires Python >=3.8, coverage is forbidden.
And because coverage (7.3.2) requires Python >=3.8
 and coverage (7.3.3) requires Python >=3.8, coverage is forbidden.
And because coverage (7.3.4) requires Python >=3.8
 and coverage (7.4.0) requires Python >=3.8, coverage is forbidden.
And because coverage (7.4.1) requires Python >=3.8
 and coverage (7.4.2) requires Python >=3.8, coverage is forbidden.
And because coverage (7.4.3) requires Python >=3.8
 and coverage (7.4.4) requires Python >=3.8, coverage is forbidden.
And because coverage (7.5.0) requires Python >=3.8
 and coverage (7.5.1) requires Python >=3.8, coverage is forbidden.
And because coverage (7.5.2) requires Python >=3.8
 and coverage (7.5.3) requires Python >=3.8, coverage is forbidden.
And because coverage (7.5.4) requires Python >=3.8
 and coverage (7.6.0) requires Python >=3.8, coverage is forbidden.
And because coverage (7.6.1) requires Python >=3.8
 and coverage (7.6.2) requires Python >=3.9, coverage is forbidden.
And because coverage (7.6.3) requires Python >=3.9
 and coverage (7.6.4) requires Python >=3.9, coverage is forbidden.
And because coverage (7.6.5) requires Python >=3.9
 and coverage (7.6.6) requires Python >=3.9, coverage is forbidden.
And because coverage (7.6.7) requires Python >=3.9
 and coverage (7.6.8) requires Python >=3.9, coverage is forbidden.
And because coverage (7.6.9) requires Python >=3.9
 and coverage (7.6.10) requires Python >=3.9, coverage is forbidden.
And because coverage (7.6.11) requires Python >=3.9
 and coverage (7.6.12) requires Python >=3.9, coverage is forbidden.
And because coverage (7.7.0) requires Python >=3.9
 and coverage (7.7.1) requires Python >=3.9, coverage is forbidden.
And because coverage (7.8.0) requires Python >=3.9
 and coverage (7.8.1) requires Python >=3.9, coverage is forbidden.
And because coverage (7.8.2) requires Python >=3.9
 and coverage (7.9.0) requires Python >=3.9, coverage is forbidden.
And because coverage (7.9.1) requires Python >=3.9
 and coverage (7.9.2) requires Python >=3.9, coverage is forbidden.
And because coverage (7.10.0) requires Python >=3.9
 and coverage (7.10.1) requires Python >=3.9, coverage is forbidden.
So, because coverage (7.10.2) requires Python >=3.9
 and bashplot depends on coverage (^7.0.0), version solving failed.

  * Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"
For coverage, a possible solution would be to set the `python` property to "<empty>"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

semanticdiff-com · 2024-06-13T19:40:38Z

Review changes with

pull-request-size bot added the size/XS label Aug 28, 2024

chore(deps): update dependency coverage to v7

210f493

renovate bot force-pushed the renovate/coverage-7.x branch from a7c40df to 210f493 Compare July 24, 2025 20:36

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency coverage to v7 #157

chore(deps): update dependency coverage to v7 #157

Uh oh!

renovate bot commented Jun 13, 2024 •

edited

Loading

Uh oh!

renovate bot commented Jun 13, 2024 •

edited

Loading

Uh oh!

semanticdiff-com bot commented Jun 13, 2024 •

edited

Loading

Uh oh!

Uh oh!

chore(deps): update dependency coverage to v7 #157

Are you sure you want to change the base?

chore(deps): update dependency coverage to v7 #157

Uh oh!

Conversation

renovate bot commented Jun 13, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Configuration

Uh oh!

renovate bot commented Jun 13, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: poetry.lock

Uh oh!

semanticdiff-com bot commented Jun 13, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

renovate bot commented Jun 13, 2024 •

edited

Loading

renovate bot commented Jun 13, 2024 •

edited

Loading

semanticdiff-com bot commented Jun 13, 2024 •

edited

Loading