Log message:
py-coverage: updated to 5.5

Version 5.5 — 2021-02-28

coverage combine has a new option, --keep to keep the original data files after \ 
combining them. The default is still to delete the files after they have been \ 
combined. This was requested in issue 1108 and implemented in pull request 1110. \ 
Thanks, Éric Larivière.
When reporting missing branches in coverage report, branches aren’t reported \ 
that jump to missing lines. This adds to the long-standing behavior of not \ 
reporting branches from missing lines. Now branches are only reported if both \ 
the source and destination lines are executed. Closes both issue 1065 and issue \ 
955.
Minor improvements to the HTML report:
The state of the line visibility selector buttons is saved in local storage so \ 
you don’t have to fiddle with them so often, fixing issue 1123.
It has a little more room for line numbers so that 4-digit numbers work well, \ 
fixing issue 1124.
Improved the error message when combining line and branch data, so that users \ 
will be more likely to understand what’s happening, closing issue 803.

Version 5.4 — 2021-01-24

The text report produced by coverage report now always outputs a TOTAL line, \ 
even if only one Python file is reported. This makes regex parsing of the output \ 
easier. Thanks, Judson Neer. This had been requested a number of times (issue \ 
1086, issue 922, issue 732).
The skip_covered and skip_empty settings in the configuration file can now be \ 
specified in the [html] section, so that text reports and HTML reports can use \ 
separate settings. The HTML report will still use the [report] settings if there \ 
isn’t a value in the [html] section. Closes issue 1090.
Combining files on Windows across drives now works properly, fixing issue 577. \ 
Thanks, Valentin Lab.
Fix an obscure warning from deep in the _decimal module, as reported in issue 1084.
Update to support Python 3.10 alphas in progress, including PEP 626: Precise \ 
line numbers for debugging and other tools.

Log message:
py-coverage: updated to 5.3.1

Version 5.3.1 --- 2020-12-19
----------------------------

- When using ``--source`` on a large source tree, v5.x was slower than previous
  versions.  This performance regression is now fixed, closing `issue 1037`_.

- Mysterious SQLite errors can happen on PyPy, as reported in `issue 1010`_. An
  immediate retry seems to fix the problem, although it is an unsatisfying
  solution.

- The HTML report now saves the sort order in a more widely supported way,
  fixing `issue 986`_.  Thanks, Sebastián Ramírez (`pull request 1066`_).

- The HTML report pages now have a :ref:`Sleepy Snake <sleepy>` favicon.

- Wheels are now provided for manylinux2010, and for PyPy3 (pp36 and pp37).

- Continuous integration has moved from Travis and AppVeyor to GitHub Actions.

Log message:
py-coverage: updated to 5.3

Version 5.3:

The source setting has always been interpreted as either a file path or a \ 
module, depending on which existed. If both interpretations were valid, it was \ 
assumed to be a file path. The new source_pkgs setting can be used to name a \ 
package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
If a plugin was disabled due to an exception, we used to still try to record its \ 
information, causing an exception, as reported in issue 1011. This is now fixed.

Log message:
py-coverage: updated to 5.2.1

Version 5.2.1
- The dark mode HTML report still used light colors for the context listing,
  making them unreadable.  This is now fixed.
- The time stamp on the HTML report now includes the time zone.

Log message:
py-coverage: updated to 5.2

Version 5.2

- The HTML report has been redesigned by Victor Salvino.  There is now a dark
  mode, the code text is larger, and system sans serif fonts are used, in
  addition to other small changes (`issue 858`_ and `pull request 931`_).

- The ``coverage report`` and ``coverage html`` commands now accept a
  ``--precision`` option to control the number of decimal points displayed.

- The ``coverage report`` and ``coverage html`` commands now accept a
  ``--no-skip-covered`` option to negate ``--skip-covered``.

- The ``--skip-empty`` option is now available for the XML report, closing
  `issue 976`_.

- The ``coverage report`` command now accepts a ``--sort`` option to specify
  how to sort the results.

- If coverage fails due to the coverage total not reaching the ``--fail-under``
  value, it will now print a message making the condition clear.

- TOML configuration files with non-ASCII characters would cause errors on
  Windows (`issue 990`_).  This is now fixed.

- The output of ``--debug=trace`` now includes information about how the
  ``--source`` option is being interpreted, and the module names being
  considered.

Log message:
pytest from versioned depends

Log message:
devel/py-coverage: skip shell portability check for unneeded file

Log message:
py-coverage: updated to 5.1

Version 5.1:
The JSON report now includes counts of covered and missing branches.
On Python 3.8, try-finally-return reported wrong branch coverage with decorated \ 
async functions (issue 964). This is now fixed.
The :meth:`~coverage.Coverage.get_option` and \ 
:meth:`~coverage.Coverage.set_option` methods can now manipulate the [paths] \ 
configuration setting.

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.