Update coverage to 4.5.1

[pyup-bot]

There's a new version of coverage available.
You are currently using 4.4.2. I have updated it to 4.5.1

These links might come in handy: PyPI | Changelog | Repo

Changelog

4.5.1

---

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

.. _issue 638: https://bitbucket.org/ned/coveragepy/issues/638/run-omit-is-ignored-since-45
.. _issue 640: https://bitbucket.org/ned/coveragepy/issues/640/indexerror-reporting-on-an-empty-decorated

.. _changes_45:

4.5

---

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

.. _issue 563: https://bitbucket.org/ned/coveragepy/issues/563/platform-specific-configuration
.. _issue 618: https://bitbucket.org/ned/coveragepy/issues/618/problem-when-combining-windows-generated
.. _issue 621: https://bitbucket.org/ned/coveragepy/issues/621/include-ignored-warning-when-using
.. _issue 622: https://bitbucket.org/ned/coveragepy/issues/622/report-omit-overwrites-run-omit
.. _issue 627: https://bitbucket.org/ned/coveragepy/issues/627/failure-generating-html-reports-when-the
.. _issue 629: https://bitbucket.org/ned/coveragepy/issues/629/multiple-use-of-combine-leads-to-empty
.. _issue 631: https://bitbucket.org/ned/coveragepy/issues/631/precise-coverage-percentage-value

.. _changes_442:

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

[pyup-bot]

Closing this in favor of #341