Update dependency coverage to v6.5.0 #316
Open
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:
==6.1.2->==6.5.0Release Notes
nedbat/coveragepy (coverage)
v6.5.0Compare Source
The JSON report now includes details of which branches were taken, and which
are missing for each file. Thanks,
Christoph Blessing <pull 1438_>. Closesissue 1425.Starting with coverage.py 6.2,
classstatements were marked as a branch.This wasn't right, and has been reverted, fixing
issue 1449_. Note thiswill very slightly reduce your coverage total if you are measuring branch
coverage.
Packaging is now compliant with
PEP 517, closingissue 1395.A new debug option
--debug=pathmapshows details of the remapping ofpaths that happens during combine due to the
[paths]setting.Fix an internal problem with caching of invalid Python parsing. Found by
OSS-Fuzz, fixing their
bug 50381_... _bug 50381: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381
.. _PEP 517: https://peps.python.org/pep-0517/
.. _issue 1395: #1395
.. _issue 1425: #1425
.. _issue 1449: #1449
.. _pull 1438: #1438
.. _changes_6-4-4:
v6.4.4Compare Source
.. _changes_6-4-3:
v6.4.3Compare Source
Fix a failure when combining data files if the file names contained glob-like
patterns. Thanks,
Michael Krebs and Benjamin Schubert <pull 1405_>_.Fix a messaging failure when combining Windows data files on a different
drive than the current directory, closing
issue 1428. Thanks,Lorenzo Micò <pull 1430_>.Fix path calculations when running in the root directory, as you might do in
a Docker container. Thanks
Arthur Rio <pull 1403_>_.Filtering in the HTML report wouldn't work when reloading the index page.
This is now fixed. Thanks,
Marc Legendre <pull 1413_>_.Fix a problem with Cython code measurement, closing
issue 972. Thanks,Matus Valo <pull 1347_>... _issue 972: #972
.. _issue 1428: #1428
.. _pull 1347: #1347
.. _pull 1403: #1403
.. _pull 1405: #1405
.. _pull 1413: #1413
.. _pull 1430: #1430
.. _changes_6-4-2:
v6.4.2Compare Source
Updated for a small change in Python 3.11.0 beta 4: modules now start with a
line with line number 0, which is ignored. This line cannot be executed, so
coverage totals were thrown off. This line is now ignored by coverage.py,
but this also means that truly empty modules (like
__init__.py) have nolines in them, rather than one phantom line. Fixes
issue 1419_.Internal debugging data added to sys.modules is now an actual module, to
avoid confusing code that examines everything in sys.modules. Thanks,
Yilei Yang <pull 1399_>_... _issue 1419: #1419
.. _pull 1399: #1399
.. _changes_6-4-1:
v6.4.1Compare Source
Greatly improved performance on PyPy, and other environments that need the
pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (
pull 1381_ andpull 1388). Slightly improved performance when using the Ctrace function, as most environments do. Closes
issue 1339.The conditions for using tomllib from the standard library have been made
more precise, so that 3.11 alphas will continue to work. Closes
issue 1390_... _issue 1339: #1339
.. _pull 1381: #1381
.. _pull 1388: #1388
.. _issue 1390: #1390
.. _changes_64:
v6.4Compare Source
withstatements could cause contained branches to beincorrectly marked as missing (
issue 1880_). This is now fixed... _issue 1880: #1880
.. _changes_7-6-3:
v6.3.3Compare Source
Closes
issue 1367_. Some results for generators may have changed... _issue 1367: #1367
.. _changes_632:
v6.3.2Compare Source
Fix: adapt to pypy3.9's decorator tracing behavior. It now traces function
decorators like CPython 3.8: both the @-line and the def-line are traced.
Fixes
issue 1326_.Debug: added
pybehaveto the list of :ref:coverage debug <cmd_debug>and :ref:
cmd_run_debugoptions.Fix: show an intelligible error message if
--concurrency=multiprocessingis used without a configuration file. Closes
issue 1320_... _issue 1320: #1320
.. _issue 1326: #1326
.. _changes_631:
v6.3.1Compare Source
Fix: deadlocks could occur when terminating processes. Some of these
deadlocks (described in
issue 1310_) are now fixed.Fix: a signal handler was being set from multiple threads, causing an error:
"ValueError: signal only works in main thread". This is now fixed, closing
issue 1312_.Fix:
--precisionon the command-line was being ignored while considering--fail-under. This is now fixed, thanks toMarcelo Trylesinski <pull 1317_>_.Fix: releases no longer provide 3.11.0-alpha wheels. Coverage.py uses CPython
internal fields which are moving during the alpha phase. Fixes
issue 1316_... _issue 1310: #1310
.. _issue 1312: #1312
.. _issue 1316: #1316
.. _pull 1317: #1317
.. _changes_63:
v6.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: #1873
.. _issue 1876: #1876
.. _changes_7-6-2:
v6.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: #1835
.. _issue 1836: #1836
.. _pull 1838: #1838
.. _pull 1843: #1843
.. _issue 1846: #1846
.. _pull 1849: #1849
.. _issue 1850: #1850
.. _pull 1851: #1851
.. _issue 1852: #1852
.. _issue 1860: #1860
.. _issue 1863: #1863
.. _changes_7-6-1:
Configuration
📅 Schedule: Branch creation - "before 1am on Tuesday" (UTC), 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 was generated by Mend Renovate. View the repository job log.