-
-
Notifications
You must be signed in to change notification settings - Fork 7
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.1 #93
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/coverage-7.x-lockfile
base: master
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-lockfile
branch
from
February 20, 2024 22:04
ee2c1fb
to
edd2345
Compare
renovate
bot
changed the title
Update dependency coverage to v7.4.1
Update dependency coverage to v7.4.2
Feb 20, 2024
renovate
bot
changed the title
Update dependency coverage to v7.4.2
Update dependency coverage to v7.4.3
Feb 23, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
February 23, 2024 22:26
edd2345
to
dfcb91b
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
March 14, 2024 20:00
dfcb91b
to
e3b38bf
Compare
renovate
bot
changed the title
Update dependency coverage to v7.4.3
Update dependency coverage to v7.4.4
Mar 14, 2024
Quality Gate passedIssues Measures |
renovate
bot
changed the title
Update dependency coverage to v7.4.4
Update dependency coverage to v7.5.0
Apr 23, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
April 23, 2024 19:07
e3b38bf
to
84b549d
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
May 4, 2024 16:21
84b549d
to
272f818
Compare
renovate
bot
changed the title
Update dependency coverage to v7.5.0
Update dependency coverage to v7.5.1
May 4, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
May 26, 2024 12:20
272f818
to
05c641d
Compare
renovate
bot
changed the title
Update dependency coverage to v7.5.1
Update dependency coverage to v7.5.2
May 26, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
May 28, 2024 16:30
05c641d
to
fe0137d
Compare
renovate
bot
changed the title
Update dependency coverage to v7.5.2
Update dependency coverage to v7.5.3
May 28, 2024
renovate
bot
changed the title
Update dependency coverage to v7.5.3
Update dependency coverage to v7.5.4
Jun 22, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
June 22, 2024 22:35
fe0137d
to
1a2478f
Compare
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
July 11, 2024 17:44
1a2478f
to
375c1fe
Compare
renovate
bot
changed the title
Update dependency coverage to v7.5.4
Update dependency coverage to v7.6.0
Jul 11, 2024
renovate
bot
force-pushed
the
renovate/coverage-7.x-lockfile
branch
from
August 4, 2024 21:54
375c1fe
to
8469e8e
Compare
renovate
bot
changed the title
Update dependency coverage to v7.6.0
Update dependency coverage to v7.6.1
Aug 4, 2024
Quality Gate passedIssues Measures |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4.0
->7.6.1
Release Notes
nedbat/coveragepy (coverage)
v7.6.1
Compare Source
Fix: coverage used to fail when measuring code using :func:
runpy.run_path <python:runpy.run_path>
with a :class:Path <python:pathlib.Path>
argument.This is now fixed, thanks to
Ask Hjorth Larsen <pull 1819_>
_.Fix: backslashes preceding a multi-line backslashed string could confuse the
HTML report. This is now fixed, thanks to
LiuYinCarl <pull 1828_>
_.Now we publish wheels for Python 3.13, both regular and free-threaded.
.. _pull 1819:https://github.com/nedbat/coveragepy/pull/18199
.. _pull 1828https://github.com/nedbat/coveragepy/pull/182828
.. _changes_7-6-0:
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 thoserequested in issues
118 <issue 118_>
(entire files),996 <issue 996_>
_ (multiple lines only when appearing together),1741 <issue 1741_>
_ (remainder of a function), and1803 <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. Thiscloses
issue 1793
_ andissue 1532
_.Fixed an incorrect calculation of "(no class)" lines in the HTML classes
report.
Python 3.13.0b3 is supported.
.. _issue 118:https://github.com/nedbat/coveragepy/issues/1188
.. _issue 996https://github.com/nedbat/coveragepy/issues/99696
.. _issue 153https://github.com/nedbat/coveragepy/issues/1532532
.. _issue 17https://github.com/nedbat/coveragepy/issues/17411741
.. _issue 1https://github.com/nedbat/coveragepy/issues/1793/1793
.. _issue https://github.com/nedbat/coveragepy/issues/1803s/1803
.. _pullhttps://github.com/nedbat/coveragepy/pull/1807ll/1807
.. _pulhttps://github.com/nedbat/coveragepy/pull/1809ull/1809
.. _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 forhelping 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_>
. Closesissue 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 byDaniel Diniz <pull 1773_>
.Fix: very complex source files like
this one <resolvent_lookup_>
_ couldcause 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 754https://github.com/nedbat/coveragepy/issues/75454
.. _issue 176https://github.com/nedbat/coveragepy/issues/1766766
.. _pull 17https://github.com/nedbat/coveragepy/pull/17681768
.. _pull 1https://github.com/nedbat/coveragepy/pull/1773/1773
.. _issue https://github.com/nedbat/coveragepy/issues/1774s/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 filecould 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 filenames 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 astring. Thanks,
Tanaydin Sirin <pull 1754_>
_. It is also now documentedon 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
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
COVERAGE_CORE=sysmon
no longer errors on 3.11 and lower,thanks
Hugo van Kemenade <pull 1747_>
_. It now issues a warning thatsys.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:
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.
This PR was generated by Mend Renovate. View the repository job log.