Log Message:
py-coverage: updated to 5.0.3

Version 5.0.3:

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

Version 5.0.2:

- Programs that used multiprocessing and changed directories would fail under
  coverage.  This is now fixed.  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.  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.  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.

- ``coverage run --debug=sys`` would fail with an AttributeError. This is now
  fixed.