Bump coverage from 6.3.2 to 6.4

[dependabot[bot]]

Bumps coverage from 6.3.2 to 6.4.

Changelog

Sourced from coverage's changelog.

Version 6.4 — 2022-05-22

• A new setting, :ref:config_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 <pull 1364_>_.

  • The timestamp and version are displayed at the top of the report. Thanks, Ammar Askar <pull 1354_>. 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 <pull 1359_>_.

• In-memory CoverageData objects now properly update(), closing issue 1323_.

.. _issue 1310: nedbat/coveragepy#1310 .. _issue 1323: nedbat/coveragepy#1323 .. _issue 1328: nedbat/coveragepy#1328 .. _issue 1351: nedbat/coveragepy#1351 .. _pull 1354: nedbat/coveragepy#1354 .. _pull 1359: nedbat/coveragepy#1359 .. _pull 1364: nedbat/coveragepy#1364

.. _changes_633:

Version 6.3.3 — 2022-05-12

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

.. _issue 1367: nedbat/coveragepy#1367

... (truncated)

Commits

• e6df5b3 fix: don't create a data file when just trying to read one. #1328
• d849b25 docs: latest sample HTML report
• 3ab15f4 build: prep for 6.4
• b5a1102 docs: spell check
• 0d8c6cb docs: mention in the man page
• 2b0f584 build: more make targets for release steps
• c739564 docs: add a note about using --debug=trace to debug No Data. #1379
• 439ccad style(docs): use definition list for warnings
• a49ca09 feat: a new debug option sqldata shows all the data being written to the db.
• 8991e9d refactor: SqliteDb uses its debug object more like other code
• 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)