Bump coverage from 5.3 to 7.2.2

[dependabot]

Bumps coverage from 5.3 to 7.2.2.

Release notes

Sourced from coverage's releases.

coverage-5.6b1

• Third-party packages are now ignored in coverage reporting. This solves a few problems:
  • Coverage will no longer report about other people’s code (issue 876). This is true even when using --source=. with a venv in the current directory.
  • Coverage will no longer generate “Already imported a file that will be measured” warnings about coverage itself (issue 905).
• The HTML report uses j/k to move up and down among the highlighted chunks of code. They used to highlight the current chunk, but 5.0 broke that behavior. Now the highlighting is working again.
• The JSON report now includes percent_covered_display, a string with the total percentage, rounded to the same number of decimal places as the other reports’ totals.

coverage-5.5

• coverage combine has a new option, --keep to keep the original data files after combining them. The default is still to delete the files after they have been combined. This was requested in issue 1108 and implemented in pull request 1110. Thanks, Éric Larivière.
• When reporting missing branches in coverage report, branches aren’t reported that jump to missing lines. This adds to the long-standing behavior of not reporting branches from missing lines. Now branches are only reported if both the source and destination lines are executed. Closes both issue 1065 and issue 955.
• Minor improvements to the HTML report:
  • The state of the line visibility selector buttons is saved in local storage so you don’t have to fiddle with them so often, fixing issue 1123.
  • It has a little more room for line numbers so that 4-digit numbers work well, fixing issue 1124.
• Improved the error message when combining line and branch data, so that users will be more likely to understand what’s happening, closing issue 803.

coverage-5.4

• The text report produced by coverage report now always outputs a TOTAL line, even if only one Python file is reported. This makes regex parsing of the output easier. Thanks, Judson Neer. This had been requested a number of times (issue 1086, issue 922, issue 732).
• The skip_covered and skip_empty settings in the configuration file can now be specified in the [html] section, so that text reports and HTML reports can use separate settings. The HTML report will still use the [report] settings if there isn’t a value in the [html] section. Closes issue 1090.
• Combining files on Windows across drives now works properly, fixing issue 577. Thanks, Valentin Lab.
• Fix an obscure warning from deep in the _decimal module, as reported in issue 1084.
• Update to support Python 3.10 alphas in progress, including PEP 626: Precise line numbers for debugging and other tools.

coverage-5.3.1

• When using --source on a large source tree, v5.x was slower than previous versions. This performance regression is now fixed, closing issue 1037.
• Mysterious SQLite errors can happen on PyPy, as reported in issue 1010. An immediate retry seems to fix the problem, although it is an unsatisfying solution.
• The HTML report now saves the sort order in a more widely supported way, fixing issue 986. Thanks, Sebastián Ramírez (pull request 1066).
• The HTML report pages now have a Sleepy Snake favicon.
• Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).
• Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

Changelog

Sourced from coverage's changelog.

Version 7.2.2 — 2023-03-16

• 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 lcov command could create a .lcov file with incorrect LF (lines found) and LH (lines hit) totals. This is now fixed, thanks to Ian Moore <pull 1583_>_.

• Fix: the coverage xml command on Windows could create a .xml file with duplicate <package> elements. This is now fixed, thanks to Benjamin Parzella <pull 1574_>, closing issue 1573.

.. _pull 1560: nedbat/coveragepy#1560 .. _issue 1573: nedbat/coveragepy#1573 .. _pull 1574: nedbat/coveragepy#1574 .. _pull 1583: nedbat/coveragepy#1583

.. _changes_7-2-1:

Version 7.2.1 — 2023-02-26

• Fix: the PyPI page had broken links to documentation pages, but no longer does, closing issue 1566_.

• Fix: public members of the coverage module are now properly indicated so that mypy will find them, fixing issue 1564_.

.. _issue 1564: nedbat/coveragepy#1564 .. _issue 1566: nedbat/coveragepy#1566

.. _changes_7-2-0:

Version 7.2.0 — 2023-02-22

• Added a new setting [report] exclude_also to let you add more exclusions without overwriting the defaults. Thanks, Alpha Chen <pull 1557_>, closing issue 1391.

• Added a :meth:.CoverageData.purge_files method to remove recorded data for a particular file. Contributed by Stephan Deibel <pull 1547_>_.

... (truncated)

Commits

• 3971cc8 docs: sample html for 7.2.2
• 4192f8b docs: prep for 7.2.2
• 021a99f fix: Remove missing type parameter (#1570)
• 4574ecf fix: don't measure all third-party packages if source is in third-party location
• dd7959d docs: wrap long lines
• f95ce97 docs: #1573 is fixed, thanks Benjamin Parzella
• 45d76fa fix: generate xml report packages correctly on windows (#1574)
• e47f354 build: will this work on fork pr's?
• dc83ac5 build: run dependency check on pushes, for more action uniformity
• 9e94ddb build: use .in from .in
• 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)

[dependabot]

The following labels could not be found: dependencies, autosquash.