Bump coverage from 5.0.1 to 5.0.2

[dependabot-preview]

Bumps coverage from 5.0.1 to 5.0.2.

Changelog

Sourced from coverage's changelog.

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

Commits

• 8d95e64 Latest sample html report
• 5b24770 Prep for 5.0.2
• 8cebaf0 Thanks, Julien Voisin for the performance improvement
• aa6d851 Improve the performances of SqliteDb._connect
• aefe08b Ensure file touching happens if nothing was measured. #884
• acf063c Suppress a warning that is not our fault
• 8a1fa7b Pedantic consistency in the changelog
• 99e7e3c 2019 -> 2020
• 89f44c1 A better name for a thing I will soon delete
• fdfc91c Don't import anything before start(). Fixes #909.
• 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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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 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 the .dependabot/config.yml file in this repo:

• Update frequency
• 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)

[coveralls]

Coverage remained the same at 98.242% when pulling 65331b2 on dependabot/pip/coverage-5.0.2 into 436dfb2 on master.

[dependabot-preview]

Dependabot tried to automerge this PR, but received the following error from GitHub:

At least 1 approving review is required by reviewers with write access.