Bump coverage[toml] from 6.2 to 6.5.0

[dependabot[bot]]

Bumps coverage[toml] from 6.2 to 6.5.0.

Release notes

Sourced from coverage[toml]'s releases.

6.5.0

• The JSON report now includes details of which branches were taken, and which are missing for each file. Thanks, Christoph Blessing (pull 1438). Closes issue 1425.
• Starting with coverage.py 6.2, class statements were marked as a branch. This wasn’t right, and has been reverted, fixing issue 1449. Note this will very slightly reduce your coverage total if you are measuring branch coverage.
• Packaging is now compliant with PEP 517, closing issue 1395.
• A new debug option --debug=pathmap shows details of the remapping of paths 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.

---

PyPI page: coverage 6.5.0

To install:

$ python3 -m pip install coverage==6.5.0

6.4.4

• Wheels are now provided for Python 3.11.

6.4.3

• Fix a failure when combining data files if the file names contained glob-like patterns (pull 1405). Thanks, Michael Krebs and Benjamin Schubert.
• Fix a messaging failure when combining Windows data files on a different drive than the current directory. (pull 1430, fixing issue 1428). Thanks, Lorenzo Micò.
• Fix path calculations when running in the root directory, as you might do in a Docker container: pull 1403, thanks Arthur Rio.
• Filtering in the HTML report wouldn’t work when reloading the index page. This is now fixed (pull 1413). Thanks, Marc Legendre.
• Fix a problem with Cython code measurement (pull 1347, fixing issue 972). Thanks, Matus Valo.

6.4.2

• 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 cannnot 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 no lines 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).

6.4.1

• Greatly improved performance on PyPy, and other environments that need the pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick (pull 1381 and pull 1388). Slightly improved performance when using the C trace 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.

6.4

• A new setting, [run] sigterm, controls whether a SIGTERM signal handler is used. In 6.3, the signal handler was always installed, to capture data at unusual process ends. Unfortunately, this introduced other problems (see issue 1310). Now the signal handler is only used if you opt-in by setting [run] sigterm = true.
• Small changes to the HTML report:
  • Added links to next and previous file, and more keyboard shortcuts: [ and ] for next file and previous file; u for up to the index; and ? to open/close the help panel. Thanks, J. M. F. Tsang.
  • The timestamp and version are displayed at the top of the report. Thanks, Ammar Askar. Closes issue 1351.
• A new debug option debug=sqldata adds more detail to debug=sql, logging all the data being written to the database.
• Previously, running coverage report (or any of the reporting commands) in an empty directory would create a .coverage data file. Now they do not, fixing issue 1328.
• On Python 3.11, the [toml] extra no longer installs tomli, instead using tomllib from the standard library. Thanks Shantanu.
• In-memory CoverageData objects now properly update(), closing issue 1323.

6.3.3

• Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again. Closes issue 1367. Some results for generators may have changed.

6.3.2

• 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 pybehave to the list of coverage debug and --debug options.

... (truncated)

Changelog

Sourced from coverage[toml]'s changelog.

Version 6.5.0 — 2022-09-29

• The JSON report now includes details of which branches were taken, and which are missing for each file. Thanks, Christoph Blessing (pull 1438). Closes issue 1425.

• Starting with coverage.py 6.2, class statements were marked as a branch. This wasn't right, and has been reverted, fixing issue 1449_. Note this will very slightly reduce your coverage total if you are measuring branch coverage.

• Packaging is now compliant with PEP 517, closing issue 1395.

• A new debug option --debug=pathmap shows details of the remapping of paths 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: nedbat/coveragepy#1395 .. _issue 1425: nedbat/coveragepy#1425 .. _pull 1438: nedbat/coveragepy#1438 .. _issue 1449: nedbat/coveragepy#1449

.. _changes_6-4-4:

Version 6.4.4 — 2022-08-16

• Wheels are now provided for Python 3.11.

.. _changes_6-4-3:

Version 6.4.3 — 2022-08-06

• Fix a failure when combining data files if the file names contained glob-like patterns (pull 1405_). Thanks, Michael Krebs and Benjamin Schubert.

• Fix a messaging failure when combining Windows data files on a different drive than the current directory. (pull 1430, fixing issue 1428). Thanks, Lorenzo Micò.

• Fix path calculations when running in the root directory, as you might do in

... (truncated)

Commits

• 0ac2453 docs: sample html report
• 0954c85 build: prep for 6.5.0
• 95195b1 docs: changelog for json report branch details
• 789f175 fix: keep negative arc values
• aabc540 feat: include branches taken and missed in JSON report. #1425
• a59fc44 docs: minor tweaks to db docs
• d296083 docs: add a note to the class-branch change
• 7f07df6 chore: make upgrade
• 6bc29a9 build: use the badge action coloring
• fd36918 fix: class statements shouldn't be branches. #1449
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)