Update dependency coverage to v4.5.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
coverage	==4.4.2 -> ==4.5.4

---

Release Notes

nedbat/coveragepy

v4.5.4

Compare Source

• Multiprocessing support in Python 3.8 was broken, but is now fixed. Closes issue 828.

➡️  PyPI page: coverage 4.5.4.
➡️  To install: python3 -m pip install coverage==4.5.4

v4.5.3

Compare Source

• Only packaging metadata changes.

v4.5.2

Compare Source

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

v4.5.1

Compare Source

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

v4.5

Compare Source

• A new kind of plugin is supported: configurers are invoked at start-up to allow more complex configuration than the .coveragerc file can easily do. See Plug-in classes 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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.