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.