build(deps-dev): Bump coverage from 4.5.3 to 5.0.4

Bumps coverage from 4.5.3 to 5.0.4.

Changelog

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.

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.

Version 5.0 --- 2019-12-14

Nothing new beyond 5.0b2.

Version 5.0b2 --- 2019-12-08

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.

The [paths] configuration section is now ordered. If you specify more than one list of patterns, the first one that matches will be used. Fixes issue 649.

The .coverage.numbits.register_sqlite_functions function now also registers numbits_to_nums for use in SQLite queries. Thanks, Simon Willison.

Python 3.9a1 is supported.

... (truncated)

Commits

d10f4b1 Correct the readme
b774e27 Latest sample HTML
b1dd5a2 Getting ready for 5.0.4
f668d6f relative_files makes XML store relative paths. #948.
fa2e0e4 Improve the changelog
ee2d1f6 sysconfig has been available since 2.7
48c73b8 htmlfiles: Handle localStorage not accessible
0f82d27 Update sphinx to handle 308 redirects
907f0e8 Use latest wheel to make Windows 3.8 work. #949
1148bf9 Fix: doc/config.rst:243: D001 Line too long
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 will not automatically merge this PR because it includes an out-of-range update to a development dependency.

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](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

percy / python-percy-client

build(deps-dev): Bump coverage from 4.5.3 to 5.0.4 #109

Version 5.0.4 --- 2020-03-16

Version 5.0.3 --- 2020-01-12

Version 5.0.2 --- 2020-01-05

Version 5.0.1 --- 2019-12-22

Version 5.0 --- 2019-12-14

Version 5.0b2 --- 2019-12-08