Log message:
py-coverage: updated to 5.0.4

Version 5.0.4:
- If using the ``[run] relative_files`` setting, the XML report will use
  relative files in the ``<source>`` elements indicating the location of source
  code.
- The textual summary report could report missing lines with negative line
  numbers on PyPy3 7.1. This is now fixed.
- Windows wheels for Python 3.8 were incorrectly built, but are now fixed.
- Updated Python 3.9 support to 3.9a4.
- HTML reports couldn't be sorted if localStorage wasn't available. This is now
  fixed: sorting works even though the sorting setting isn't retained.

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.

Log message:
py-coverage: updated to 5.0.1

Version 5.0.1:

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

Log message:
py-coverage: updated to 5.0

Major changes in 5.0

This is an overview of the changes in 5.0 since the last version of 4.5.x. This \ 
is not a complete list of all changes. See the complete change history for all \ 
the details.

Open Questions

How to support SQL access to data? The database schema has to be convenient and \ 
efficient for coverage.py’s execution, which would naturally make it an \ 
internal implementation detail. But the coverage data is now more complex, and \ 
SQL access could be a powerful way to access it, pointing toward a public \ 
guaranteed schema. What’s the right balance?

Backward Incompatibilities

Python 2.6, 3.3 and 3.4 are no longer supported.
The CoverageData interface is still public, but has changed.
The data file is now created earlier than it used to be. In some circumstances, \ 
you may need to use parallel=true to avoid multiple processes overwriting each \ 
others’ data.
When constructing a coverage.Coverage object, data_file can be specified as None \ 
to prevent writing any data file at all. In previous versions, an explicit \ 
data_file=None argument would use the default of “.coverage”. Fixes issue \ 
871.
The [run] note setting has been deprecated. Using it will result in a warning, \ 
and the note will not be written to the data file. The corresponding \ 
CoverageData methods have been removed.
The deprecated Reporter.file_reporters property has been removed.
The reporting methods used to permanently apply their arguments to the \ 
configuration of the Coverage object. Now they no longer do. The arguments \ 
affect the operation of the method, but do not persist.

New Features

Coverage.py can now record the context in which each line was executed. The \ 
contexts are stored in the data file and can be used to drill down into why a \ 
particular line was run. Static contexts let you specify a label for an entire \ 
coverage run, for example to separate coverage for different operating systems \ 
or versions of Python. Dynamic contexts can change during a single measurement \ 
run. This can be used to record the names of the tests that executed each line. \ 
See Measurement contexts for full information.
Coverage’s data storage has changed. In version 4.x, .coverage files were \ 
basically JSON. Now, they are SQLite databases. The database schema is \ 
documented (Coverage.py database schema), but might still be in flux.
Data can now be “reported” in JSON format, for programmatic use, as \ 
requested in issue 720. The new coverage json command writes raw and summarized \ 
data to a JSON file. Thanks, Matt Bachmann.
Configuration can now be read from TOML files. This requires installing \ 
coverage.py with the [toml] extra. The standard “pyproject.toml” file will \ 
be read automatically if no other configuration file is found, with settings in \ 
the [tool.coverage.] namespace. Thanks to Frazer McLean for implementation and \ 
persistence. Finishes issue 664.
The HTML and textual reports now have a --skip-empty option that skips files \ 
with no statements, notably __init__.py files. Thanks, Reya B.
You can specify the command line to run your program with the [run] command_line \ 
configuration setting, as requested in issue 695.
An experimental [run] relative_files setting tells coverage to store relative \ 
file names in the data file. This makes it easier to run tests in one (or many) \ 
environments, and then report in another. It has not had much real-world \ 
testing, so it may change in incompatible ways in the future.
Environment variable substitution in configuration files now supports two \ 
syntaxes for controlling the behavior of undefined variables: if VARNAME is not \ 
defined, ${VARNAME?} will raise an error, and ${VARNAME-default value} will use \ 
“default value”.
The location of the configuration file can now be specified with a \ 
COVERAGE_RCFILE environment variable, as requested in issue 650.
A new warning (already-imported) is issued if measurable files have already been \ 
imported before coverage.py started measurement. See Warnings for more \ 
information.
Error handling during reporting has changed slightly. All reporting methods now \ 
behave the same. The --ignore-errors option keeps errors from stopping the \ 
reporting, but files that couldn’t parse as Python will always be reported as \ 
warnings. As with other warnings, you can suppress them with the [run] \ 
disable_warnings configuration setting.
Added the classmethod Coverage.current() to get the latest started Coverage instance.

Bugs Fixed

The coverage run command has always adjusted the first entry in sys.path, to \ 
properly emulate how Python runs your program. Now this adjustment is skipped if \ 
sys.path[0] is already different than Python’s default. This fixes issue 715.
Python files run with -m now have __spec__ defined properly. This fixes issue \ 
745 (about not being able to run unittest tests that spawn subprocesses), and \ 
issue 838, which described the problem directly.
Coverage will create directories as needed for the data file if they don’t \ 
exist, closing issue 721.
fail_under values more than 100 are reported as errors. Thanks to Mike Fiedler \ 
for closing issue 746.
The “missing” values in the text output are now sorted by line number, so \ 
that missing branches are reported near the other lines they affect. The values \ 
used to show all missing lines, and then all missing branches.
Coverage.py no longer fails if the user program deletes its current directory.

Log message:
py-coverage: updated to 4.5.4

Version 4.5.4:
- Multiprocessing support in Python 3.8 was broken, but is now fixed.

Log message:
py-coverage: updated to 4.5.3

Version 4.5.3:
- Only packaging metadata changes.

Log message:
py-coverage: updated to 4.5.2

Version 4.5.2:
- Namespace packages are supported on Python 3.7, where they used to cause
  TypeErrors about path being None.
- Python 3.8 (as of today!) passes all tests.
- Development moved from Bitbucket to GitHub.

Log message:
py-coverage: updated to 4.5.1

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

Log message:
py-coverage: updated to 4.5

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

Log message:
py-coverage: use ALTERNATIVES; PLIST changed to avoid conflicts between Python \ 
versions; bumped revision