Update dependency coverage to v5

[renovate]

This PR contains the following updates:

Package	Update	Change
coverage	major	==4.5.4 -> ==5.0.3

---

Release Notes

nedbat/coveragepy

v5.0.3

Compare Source

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

.. _issue 862: #​862
.. _issue 916: #​916

.. _changes_502:

v5.0.2

Compare Source

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

.. _issue 884: #​884
.. _issue 890: #​890
.. _issue 891: #​891
.. _issue 901: #​901
.. _issue 907: #​907
.. _issue 909: #​909

.. _changes_501:

v5.0.1

Compare Source

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

.. _issue 880: #​880
.. _issue 886: #​886
.. _issue 895: #​895
.. _issue 899: #​899
.. _issue 900: #​900

.. _changes_50:

v5.0

Compare Source

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

.. _issue 862: #​862
.. _issue 916: #​916

.. _changes_502:

---

Renovate configuration

📅 Schedule: 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 WhiteSource Renovate. View repository job log here.