Bump coverage from 5.1 to 5.3

[dependabot]

Bumps coverage from 5.1 to 5.3.

Release notes

Sourced from coverage's releases.

coverage-5.3

• The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
• If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

coverage-5.2.1

• The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
• The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

coverage-5.2

• The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858 and pull request 931).
• The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982).
• The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779 and pull request 932).
• The --skip-empty option is now available for the XML report, closing issue 976.
• The coverage report command now accepts a --sort option to specify how to sort the results. Thanks, Jerin Peter George (pull request 1005).
• If coverage fails due to the coverage total not reaching the --fail-under value, it will now print a message making the condition clear. Thanks, Naveen Yadav (pull request 977).
• TOML configuration files with non-ASCII characters would cause errors on Windows (issue 990). This is now fixed.
• The output of --debug=trace now includes information about how the --source option is being interpreted, and the module names being considered.

Changelog

Sourced from coverage's changelog.

Version 5.3 --- 2020-09-13

• The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268_.

• If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011_. This is now fixed.

.. _issue 268: nedbat/coveragepy#268 .. _issue 1011: nedbat/coveragepy#1011

.. _changes_521:

Version 5.2.1 --- 2020-07-23

• The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009_). This is now fixed.

• The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960_).

.. _pull request 960: nedbat/coveragepy#960 .. _issue 1009: nedbat/coveragepy#1009

.. _changes_52:

Version 5.2 --- 2020-07-05

• The HTML report has been redesigned by Vince Salvino. There is now a dark mode, the code text is larger, and system sans serif fonts are used, in addition to other small changes (issue 858_ and pull request 931_).

• The coverage report and coverage html commands now accept a --precision option to control the number of decimal points displayed. Thanks, Teake Nutma (pull request 982_).

• The coverage report and coverage html commands now accept a --no-skip-covered option to negate --skip-covered. Thanks, Anthony Sottile (issue 779_ and pull request 932_).

• The --skip-empty option is now available for the XML report, closing

... (truncated)

Commits

• d13594e Making a release
• 039ef09 If a plugin is disabled, don't try to record its file tracers. #1011
• 24eb6fd Move disable_plugin to Python
• 987ceb9 Fix a missed exception handling for bad plugins
• c907b2e ambigious -> ambiguous
• 263f3e1 Docs and cleanup for source_pkgs
• ecd6ab1 Create Way to force package even if filepath exists (#1026)
• 39e6d1d Thomas Grainger's first commit
• 154f528 replace confusing comment with assertion (#1028)
• c315908 Explain a mystery
• 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)