Bump coverage from 4.2 to 4.5.3

[dependabot-preview]

Bumps coverage from 4.2 to 4.5.3.

Changelog

Sourced from coverage's changelog.

Version 4.5.3 -- 2019-03-09

• Only packaging metadata changes.

Version 4.5.2 --- 2018-11-12

• Namespace packages are supported on Python 3.7, where they used to cause TypeErrors about path being None. Fixes issue 700.
• Python 3.8 (as of today!) passes all tests. Fixes issue 707 and issue 714.
• Development moved from Bitbucket to GitHub.

Version 4.5.1 --- 2018-02-10

• Now that 4.5 properly separated the [run] omit and [report] omit settings, an old bug has become apparent. If you specified a package name for [run] source, then omit patterns weren't matched inside that package. This bug (issue 638) is now fixed.
• On Python 3.7, reporting about a decorated function with no body other than a docstring would crash coverage.py with an IndexError (issue 640). This is now fixed.
• Configurer plugins are now reported in the output of --debug=sys.

Version 4.5 --- 2018-02-03

• A new kind of plugin is supported: configurators are invoked at start-up to allow more complex configuration than the .coveragerc file can easily do. See api_plugin for details. This solves the complex configuration problem described in issue 563.
• The fail_under option can now be a float. Note that you must specify the [report] precision configuration option for the fractional part to be used. Thanks to Lars Hupfeldt Nielsen for help with the implementation. Fixes issue 631.
• The include and omit options can be specified for both the [run] and [report] phases of execution. 4.4.2 introduced some incorrect interactions between those phases, where the options for one were confused for the other. This is now corrected, fixing issue 621 and issue 622. Thanks to Daniel Hahler for seeing more clearly than I could.
• The coverage combine command used to always overwrite the data file, even when no data had been read from apparently combinable files. Now, an error is raised if we thought there were files to combine, but in fact none of them could be used. Fixes issue 629.
• The coverage combine command could get confused about path separators when combining data collected on Windows with data collected on Linux, as described in issue 618. This is now fixed: the result path always uses the path separator specified in the [paths] result.
• On Windows, the HTML report could fail when source trees are deeply nested, due to attempting to create HTML filenames longer than the 250-character maximum. Now filenames will never get much larger than 200 characters, fixing issue 627. Thanks to Alex Sandro for helping with the fix.

Version 4.4.2 --- 2017-11-05

• Support for Python 3.7. In some cases, class and module docstrings are no longer counted in statement totals, which could slightly change your total results.
• Specifying both --source and --include no longer silently ignores the include setting, instead it displays a warning. Thanks, Loïc Dachary. Closes issue 265 and issue 101.
• Fixed a race condition when saving data and multiple threads are tracing (issue 581). It could produce a "dictionary changed size during iteration" RuntimeError. I believe this mostly but not entirely fixes the race condition. A true fix would likely be too expensive. Thanks, Peter Baughman for the debugging, and Olivier Grisel for the fix with tests.
• Configuration values which are file paths will now apply tilde-expansion, closing issue 589.
• Now secondary config files like tox.ini and setup.cfg can be specified explicitly, and prefixed sections like [coverage:run] will be read. Fixes issue 588.
• Be more flexible about the command name displayed by help, fixing issue 600. Thanks, Ben Finney.

Version 4.4.1 --- 2017-05-14

• No code changes: just corrected packaging for Python 2.7 Linux wheels.

Version 4.4 --- 2017-05-07

• Reports could produce the wrong file names for packages, reporting pkg.py instead of the correct pkg/__init__.py. This is now fixed. Thanks, Dirk Thomas.
• XML reports could produce <source> and <class> lines that together didn't specify a valid source file path. This is now fixed. (issue 526)
• Namespace packages are no longer warned as having no code. (issue 572)

... (truncated)

Commits

• f205ed3 Latest howto tweaks
• 5d7d2cc Latest sample HTML
• 9885b6e Paperwork for 4.5.3
• 48b2517 doc8 merged my -q option
• bc2f00f Fix a test that still thought we were on bitbucket
• 56e8fe1 Use a full URL for the Tidelift logo
• 059daf6 Fix a few last Bitbucket references #731
• 69e0a45 Oops, had tidelift twice
• 2d963c8 Correct a link
• b17d9f7 Bump version
• 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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major 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)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• 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)

Finally, you can contact us by mentioning @dependabot.