Bump coverage from 5.0 to 5.0.3

Bumps coverage from 5.0 to 5.0.3.

Changelog

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.

Commits

5e4681e Note two additions
f15b16d Prep for 5.0.3
6c9b729 Include SQLite compile_options in "debug sys"
0b4eeed Improvements to debugging while chasing #915
70d527b Refine the conditions for tweaking sys.path[0]. Fixes #862
1c653dd "coverage debug premain"
d10e03c A test of running coverage when it has been zipped. #862
d197d9c A test that reproduces #862
648b136 bpo39166 is fixed
6d6af17 tox anypy environment
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](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) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)

django-oscar / django-oscar-accounts

Bump coverage from 5.0 to 5.0.3 #84

Version 5.0.3 --- 2020-01-12

Version 5.0.2 --- 2020-01-05

Version 5.0.1 --- 2019-12-22

Codecov Report