-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency coverage to v7.6.10 #282
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/coverage-7.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
October 12, 2024 04:27
122a3a1
to
f79396f
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.2
Update dependency coverage to v7.6.3
Oct 14, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
October 14, 2024 01:13
f79396f
to
2f60c8c
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
3 times, most recently
from
October 20, 2024 06:06
03f82a1
to
f19a216
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.3
Update dependency coverage to v7.6.4
Oct 21, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
October 21, 2024 00:28
f19a216
to
925b688
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
2 times, most recently
from
October 26, 2024 06:08
1ff65b4
to
f19c331
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
October 27, 2024 12:36
f19c331
to
815fca9
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
October 27, 2024 21:56
815fca9
to
1fe94be
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
2 times, most recently
from
November 9, 2024 03:35
287cf11
to
dd93b10
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
November 14, 2024 18:51
dd93b10
to
bad6b7b
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.4
Update dependency coverage to v7.6.5
Nov 14, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
November 16, 2024 03:23
6677ee9
to
ce24c29
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
November 23, 2024 03:24
ce24c29
to
ba8fde6
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.7
Update dependency coverage to v7.6.8
Nov 24, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
November 24, 2024 04:41
ba8fde6
to
7616469
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
2 times, most recently
from
December 1, 2024 16:58
777aad5
to
8935058
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.8
Update dependency coverage to v7.6.9
Dec 6, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
December 6, 2024 12:42
8935058
to
8def8af
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
2 times, most recently
from
December 14, 2024 04:12
44498e2
to
d7e6d18
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
3 times, most recently
from
December 22, 2024 01:42
ec31b6a
to
6197839
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.9
Update dependency coverage to v7.6.10
Dec 26, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
December 26, 2024 18:26
6197839
to
dfcf674
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
3 times, most recently
from
January 4, 2025 03:38
02a43ec
to
1ddc173
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
January 11, 2025 05:55
1ddc173
to
cb1ea1b
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
January 19, 2025 12:23
cb1ea1b
to
4398424
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
January 26, 2025 12:43
4398424
to
d3587f2
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x
branch
from
February 1, 2025 22:21
d3587f2
to
58b649e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.6.10
Release Notes
nedbat/coveragepy (coverage)
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
_ 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 bisect
helped find it,and now it's fixed.
Docs: re-wrote the :ref:
subprocess
page to put multiprocessing first and tohighlight 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#pep-649-deferred-evaluation-of-annotations
.. _changes_7-6-9:
v7.6.9
Compare Source
Tomas Uribe fixed <pull 1901_>
_ a performance problem in the XMLreport. 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
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6
Compare Source
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
with
statements could cause contained branches to beincorrectly 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 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: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
, 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: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:
Configuration
📅 Schedule: Branch creation - "* * * * 0,6" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.