-
Notifications
You must be signed in to change notification settings - Fork 32
chore(deps): update dependency coverage to v7.8.0 - autoclosed #218
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
Closed
Conversation
This file contains hidden or 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
03d2e7b to
52dca76
Compare
52dca76 to
8896009
Compare
8896009 to
5d5aea6
Compare
5d5aea6 to
d1e1329
Compare
d1e1329 to
3d2760c
Compare
3d2760c to
3b202f6
Compare
3b202f6 to
7cda854
Compare
7cda854 to
3143886
Compare
3143886 to
b6a8550
Compare
b6a8550 to
a79a838
Compare
a79a838 to
aabbd6b
Compare
ee5441d to
f5dff53
Compare
d1bc47f to
10e7240
Compare
10e7240 to
50c9496
Compare
50c9496 to
8a6549c
Compare
8a6549c to
3a6c7d9
Compare
3a6c7d9 to
91e22aa
Compare
91e22aa to
a9a929c
Compare
a9a929c to
5562263
Compare
5562263 to
800083e
Compare
800083e to
b444809
Compare
b444809 to
60cccff
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.2.1->7.8.0Release Notes
nedbat/coveragepy (coverage)
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: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.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:https://github.com/nedbat/coveragepy/issues/18888
.. _pull 1919https://github.com/nedbat/coveragepy/pull/191919
.. _changes_7-6-12:
v7.6.12Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927:https://github.com/nedbat/coveragepy/issues/19277
.. _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: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.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: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.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:https://github.com/nedbat/coveragepy/pull/19011
.. _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:https://github.com/nedbat/coveragepy/issues/18966
.. _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:https://github.com/nedbat/coveragepy/issues/18911
.. _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:https://github.com/pytest-dev/pytest-cov/issues/6666
.. _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:https://github.com/nedbat/coveragepy/issues/18800
.. _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:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676
.. _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: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.1Compare Source
issue 1927_). These are nowbuilding reliably.
.. _issue 1927:https://github.com/nedbat/coveragepy/issues/19277
.. _changes_7-6-11:
v7.6.0Compare 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_excludesection 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.4Compare 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.3Compare 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.2Compare 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.1Compare 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.0Compare 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.4Compare 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:formatsetting 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.3Compare 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.2Compare Source
COVERAGE_CORE=sysmonno 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.1Compare 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.0Compare Source
:mod:
sys.monitoring <python:sys.monitoring>module by defining aCOVERAGE_CORE=sysmonenvironment 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.4Compare 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.3Compare 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.pyandfile001.py. Fixesissue 1709_.The
coverage annotatecommand 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>:pytestwrites the pytest test name into the debug output.dataop2writes 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.2Compare Source
The
coverage lcovcommand ignored the[report] exclude_linesand[report] exclude_alsosettings (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
typeis 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.1Compare 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.0Compare Source
Added a :meth:
.Coverage.collectcontext 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
nosemgrepcomments 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:
v7.2.7Compare Source
Fix: reverted a
change from 6.4.3 <pull 1347b_>_ that helped Cython, butalso 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 arecent change (
issue 1538 <issue 1538b_>). Thanks toAnders Kaseorg <pull 1629_>_ and David Szotten for persisting with problem reports anddetailed 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.6Compare Source
Fix: the
lcovcommand could raise an IndexError exception if a file istranslated 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 syscommand includes some environment variablesin 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.5Compare Source
html_report()could fail with an AttributeError onisattyif runin an unusual environment where sys.stdout had been replaced. This is now
fixed.
.. _changes_7-2-4:
v7.2.4Compare Source
PyCon 2023 sprint fixes!
Fix: with
relative_files = true, specifying a specific file to include oromit wouldn't work correctly (
issue 1604). This is now fixed, withtesting help by
Marc Gibbons <pull 1608_>.Fix: the XML report would have an incorrect
<source>element when usingrelative 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 toRicardo Newbery <pull 1613_>_.Docs: a new :ref:
Migrating page <migrating>with details about how tomigrate 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.3Compare Source
Fix: the :ref:
config_run_sigtermsetting was meant to capture data if aprocess was terminated with a SIGTERM signal, but it didn't always. This was
fixed thanks to
Lewis Gaul <pull 1600_>, closingissue 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 toOleh 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.2Compare 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 lcovcommand could create a .lcov file with incorrectLF (lines found) and LH (lines hit) totals. This is now fixed, thanks to
Ian Moore <pull 1583_>_.Fix: the
coverage xmlcommand on Windows could create a .xml file withduplicate
<package>elements. This is now fixed, thanks toBenjamin Parzella <pull 1574_>, closingissue 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:
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.