-
Notifications
You must be signed in to change notification settings - Fork 0
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
chore(deps): update dependency coverage to v7.5.3 - autoclosed #88
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #88 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 19 19
Lines 640 640
Branches 57 57
=========================================
Hits 640 640
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
58c78b6
to
9f5c239
Compare
9f5c239
to
f1b8035
Compare
f1b8035
to
4883f76
Compare
4883f76
to
6f6e9b1
Compare
6f6e9b1
to
4f9769a
Compare
4f9769a
to
26fa041
Compare
26fa041
to
1ad729d
Compare
1ad729d
to
4e36e1e
Compare
4e36e1e
to
45a1596
Compare
This PR contains the following updates:
7.2.7
->7.5.3
Release Notes
nedbat/coveragepy (coverage)
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:
v7.4.0
Compare Source
:mod:
sys.monitoring <python:sys.monitoring>
module by defining aCOVERAGE_CORE=sysmon
environment variable. This should be faster forline 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
andfile001.py
. Fixesissue 1709
_.The
coverage annotate
command used to announce that it would be removedin 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 toBrad 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_>
, whoprovided patient detailed diagnosis <pull 1650_>
andgraciously 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
.. _starbadhttps://github.com/nedbat/coveragepy/issues/1407#issuecomment-163108520909
.. _pull 165https://github.com/nedbat/coveragepy/pull/1650650
.. _changes_7-3-0:
v7.3.0
Compare Source
Added a :meth:
.Coverage.collect
context manager to start and stop coveragedata 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, closingissue 1646
_. Thanksto 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 thatsemgrep-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:
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 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 has been generated by Mend Renovate. View repository job log here.