chore: bump coverage from 4.4.1 to 5.2

[dependabot-preview]

Bumps coverage from 4.4.1 to 5.2.

Release notes

Sourced from coverage's releases.

coverage-5.2

• The HTML report has been redesigned by Victor 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.

coverage-5.1

• The JSON report now includes counts of covered and missing branches. Thanks, Salvatore Zagaria.
• On Python 3.8, try-finally-return reported wrong branch coverage with decorated async functions (issue 964). This is now fixed. Thanks, Kjell Braden.
• The https://github.com/nedbat/coveragepy/blob/HEAD[https://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD\https://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADnhttps://github.com/nedbat/coveragepy/blob/HEAD(https://github.com/nedbat/coveragepy/blob/HEAD)https://github.com/nedbat/coveragepy/blob/HEAD]https://github.com/nedbat/coveragepy/blob/HEAD(https://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADchttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADshttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD#https://github.com/nedbat/coveragepy/blob/HEADchttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADChttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADnhttps://github.com/nedbat/coveragepy/blob/HEAD)https://github.com/nedbat/coveragepy/blob/HEAD and https://github.com/nedbat/coveragepy/blob/HEAD[https://github.com/nedbat/coveragepy/blob/HEADshttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD\https://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADnhttps://github.com/nedbat/coveragepy/blob/HEAD(https://github.com/nedbat/coveragepy/blob/HEAD)https://github.com/nedbat/coveragepy/blob/HEAD]https://github.com/nedbat/coveragepy/blob/HEAD(https://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADchttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADshttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD#https://github.com/nedbat/coveragepy/blob/HEADchttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADChttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADvhttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADrhttps://github.com/nedbat/coveragepy/blob/HEADahttps://github.com/nedbat/coveragepy/blob/HEADghttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEAD.https://github.com/nedbat/coveragepy/blob/HEADshttps://github.com/nedbat/coveragepy/blob/HEADehttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEAD_https://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADphttps://github.com/nedbat/coveragepy/blob/HEADthttps://github.com/nedbat/coveragepy/blob/HEADihttps://github.com/nedbat/coveragepy/blob/HEADohttps://github.com/nedbat/coveragepy/blob/HEADnhttps://github.com/nedbat/coveragepy/blob/HEAD)https://github.com/nedbat/coveragepy/blob/HEAD methods can now manipulate the [paths] configuration setting. Thanks to Bernát Gábor for the fix for issue 967.

coverage-5.0.4

• If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
• The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
• Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
• Updated Python 3.9 support to 3.9a4.
• HTML reports couldn’t be sorted if localStorage wasn’t available. This is now fixed: sorting works even though the sorting setting isn’t retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.

coverage-5.0.3

• A performance improvement in 5.0.2 didn’t work for test suites that changed directory before combining data, causing “Couldn’t use data file: no such table: meta” errors (issue 916). This is now fixed.
• Coverage could fail to run your program with some form of “ModuleNotFound” or “ImportError” trying to import from the current directory. This would happen if coverage had been packaged into a zip file (for example, on Windows), or was found indirectly (for example, by pyenv-virtualenv). A number of different scenarios were described in issue 862 which is now fixed. Huge thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and George-Cristian Bîrzan for protracted debugging sessions.
• Added the “premain” debug option.
• Added SQLite compile-time options to the “debug sys” output.

coverage-5.0.2

• Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (issue 890). A side effect is that debug information about the config files read now shows absolute paths to the files.
• When running programs as modules (coverage run -m) with --source, some measured modules were imported before coverage starts. This resulted in unwanted warnings (“Already imported a file that will be measured”) and a reduction in coverage totals (issue 909). This is now fixed.
• If no data was collected, an exception about “No data to report” could happen instead of a 0% report being created (issue 884). This is now fixed.
• The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in issue 891. Now, those files will not be measured, since their data would not be recordable.
• A new warning (“dynamic-conflict”) is issued if two mechanisms are trying to change the dynamic context. Closes issue 901.
• coverage run --debug=sys would fail with an AttributeError. This is now fixed (issue 907).

coverage-5.0.1

• If a 4.x data file is the cause of a “file is not a database” error, then use a more specific error message, “Looks like a coverage 4.x data file, are you mixing versions of coverage?” Helps diagnose the problems described in issue 886.
• Measurement contexts and relative file names didn’t work together, as reported in issue 899 and issue 900. This is now fixed, thanks to David Szotten.
• When using coverage run --concurrency=multiprocessing, all data files should be named with parallel-ready suffixes. 5.0 mistakenly named the main process’ file with no suffix when using --append. This is now fixed, closing issue 880.
• Fixed a problem on Windows when the current directory is changed to a different drive (issue 895). Thanks, Olivier Grisel.
• Updated Python 3.9 support to 3.9a2.

coverage-5.0

Nothing new beyond 5.0b2.

coverage-5.0b2

• An experimental [run] relative_files setting tells coverage to store relative file names in the data file. This makes it easier to run tests in one (or many) environments, and then report in another. It has not had much real-world testing, so it may change in incompatible ways in the future.
• When constructing a coverage.Coverage object, data_file can be specified as None to prevent writing any data file at all. In previous versions, an explicit data_file=None argument would use the default of “.coverage”. Fixes issue 871.
• Python files run with -m now have __spec__ defined properly. This fixes issue 745 (about not being able to run unittest tests that spawn subprocesses), and issue 838, which described the problem directly.

Changelog

Sourced from coverage's changelog.

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 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.

Version 5.1 --- 2020-04-12

• The JSON report now includes counts of covered and missing branches. Thanks, Salvatore Zagaria.
• On Python 3.8, try-finally-return reported wrong branch coverage with decorated async functions (issue 964). This is now fixed. Thanks, Kjell Braden.
• The ~coverage.Coverage.get_option and ~coverage.Coverage.set_option methods can now manipulate the [paths] configuration setting. Thanks to Bernát Gábor for the fix for issue 967.

Version 5.0.4 --- 2020-03-16

• If using the [run] relative_files setting, the XML report will use relative files in the <source> elements indicating the location of source code. Closes issue 948.
• The textual summary report could report missing lines with negative line numbers on PyPy3 7.1 (issue 943). This is now fixed.
• Windows wheels for Python 3.8 were incorrectly built, but are now fixed. (issue 949)
• Updated Python 3.9 support to 3.9a4.
• HTML reports couldn't be sorted if localStorage wasn't available. This is now fixed: sorting works even though the sorting setting isn't retained. (issue 944 and pull request 945). Thanks, Abdeali Kothari.

Version 5.0.3 --- 2020-01-12

• A performance improvement in 5.0.2 didn't work for test suites that changed directory before combining data, causing "Couldn't use data file: no such table: meta" errors (issue 916). This is now fixed.
• Coverage could fail to run your program with some form of "ModuleNotFound" or "ImportError" trying to import from the current directory. This would happen if coverage had been packaged into a zip file (for example, on Windows), or was found indirectly (for example, by pyenv-virtualenv). A number of different scenarios were described in issue 862 which is now fixed. Huge thanks to Agbonze O. Jeremiah for reporting it, and Alexander Waters and George-Cristian Bîrzan for protracted debugging sessions.
• Added the "premain" debug option.
• Added SQLite compile-time options to the "debug sys" output.

Version 5.0.2 --- 2020-01-05

• Programs that used multiprocessing and changed directories would fail under coverage. This is now fixed (issue 890). A side effect is that debug information about the config files read now shows absolute paths to the files.
• When running programs as modules (coverage run -m) with --source, some measured modules were imported before coverage starts. This resulted in unwanted warnings ("Already imported a file that will be measured") and a reduction in coverage totals (issue 909). This is now fixed.
• If no data was collected, an exception about "No data to report" could happen instead of a 0% report being created (issue 884). This is now fixed.
• The handling of source files with non-encodable file names has changed. Previously, if a file name could not be encoded as UTF-8, an error occurred, as described in issue 891. Now, those files will not be measured, since their data would not be recordable.
• A new warning ("dynamic-conflict") is issued if two mechanisms are trying to change the dynamic context. Closes issue 901.
• coverage run --debug=sys would fail with an AttributeError. This is now fixed (issue 907).

Version 5.0.1 --- 2019-12-22

• If a 4.x data file is the cause of a "file is not a database" error, then use a more specific error message, "Looks like a coverage 4.x data file, are you mixing versions of coverage?" Helps diagnose the problems described in issue 886.

Commits

• 12bb9f2 More uniformity in howto.txt
• da2fc7d Last tweaks before 5.2
• 29ea33b Make sure Appveyor uses the latest versions
• 1a2ed8f A known failure has been fixed
• 085e18b gevent is still an issue
• f3fa80e Maybe tox-battery will be better in the future
• 6c0bb84 Latest sample_html report
• 22c6bcd Fix wheel-making
• 7a84f2e New cmd_help needs to be built for 'tox -e doc'
• b4683d3 Don't check our own readthedocs links
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[satya7289]

Fixed in this PR

[sakshi1499]

Closing this #578 does the same thing.

[dependabot-preview]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.