- Switch off test_debug_trace started to avoid failure
(gh#nedbat/coveragepy#1161).
- Update to 5.5:
- 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.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=92
- 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
- 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.
- Combining files on Windows across drives how works properly
- 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 <pep626_>`_.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=90
- 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).
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=88
- update for singlespec
- update to 4.3.4:
- Using the --skip-covered option on an HTML report with 100% coverage would
cause a “No data to report” error, as reported in issue 549. This is now
fixed; thanks, Loïc Dachary.
- If-statements can be optimized away during compilation, for example, if 0:
or if __debug__:. Coverage.py had problems properly understanding these
statements which existed in the source, but not in the compiled bytecode.
This problem, reported in issue 522, is now fixed.
- If you specified --source as a directory, then coverage.py would look for
importable Python files in that directory, and could identify ones that had
never been executed at all. But if you specified it as a package name, that
detection wasn’t performed. Now it is, closing issue 426. Thanks to Loïc
Dachary for the fix.
- If you started and stopped coverage measurement thousands of times in your
process, you could crash Python with a “Fatal Python error: deallocating
None” error. This is now fixed. Thanks to Alex Groce for the bug report.
- On PyPy, measuring coverage in subprocesses could produce a warning: “Trace
function changed, measurement is likely wrong: None”. This was spurious,
and has been suppressed.
- Previously, coverage.py couldn’t start on Jython, due to that
implementation missing the multiprocessing module (issue 551). This problem
has now been fixed. Also, issue 322 about not being able to invoke coverage
conveniently, seems much better: jython -m coverage run myprog.py works
properly.
- Let’s say you ran the HTML report over and over again in the same output
directory, with --skip-covered. And imagine due to your heroic test-writing
efforts, a file just acheived the goal of 100% coverage. With coverage.py
4.3, the old HTML file with the less-than-100% coverage would be left
behind. This file is now properly deleted.
OBS-URL: https://build.opensuse.org/request/show/479281
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=54
- update to Version 4.3.1 — 2016-12-28:
- Some environments couldn’t install 4.3, as described in issue 540. This is
now fixed.
- The check for conflicting --source and --include was too simple in a few
different ways, breaking a few perfectly reasonable use cases, described in
issue 541. The check has been reverted while we re-think the fix for issue 265.
- update to Version 4.3 — 2016-12-27:
Special thanks to Loïc Dachary, who took an extraordinary interest in
coverage.py and contributed a number of improvements in this release.
- The HTML report now supports a --skip-covered option like the other
reporting commands. Thanks, Loïc Dachary for the implementation, closing
issue 433.
- Subprocesses that are measured with automatic subprocess measurement used
to read in any pre-existing data file. This meant data would be incorrectly
carried forward from run to run. Now those files are not read, so each
subprocess only writes its own data. Fixes issue 510.
- Coverage.py wouldn’t execute sys.excepthook when an exception happened in
your program. Now it does, thanks to Andrew Hoos. Closes issue 535.
- The coverage combine command will now fail if there are no data files to
combine. The combine changes in 4.2 meant that multiple combines could lose
data, leaving you with an empty .coverage data file. Fixes issues issue 525,
issue 412, issue 516, and probably issue 511.
- The branch coverage issues described in issue 493, issue 496, and issue 502
are now fixed, thanks to Loïc Dachary.
- Options can now be read from a tox.ini file, if any. Like setup.cfg,
sections are prefixed with “coverage:”, so [run] options will be read from
the [coverage:run] section of tox.ini. Implements part of issue 519. Thanks,
Stephen Finucane.
- Specifying both --source and --include no longer silently ignores the
include setting, instead it fails with a message. Thanks, Nathan Land and
OBS-URL: https://build.opensuse.org/request/show/450363
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=52
- Since ``concurrency=multiprocessing`` uses subprocesses, options specified on
the coverage.py command line will not be communicated down to them. Only
options in the configuration file will apply to the subprocesses.
Previously, the options didn't apply to the subprocesses, but there was no
indication. Now it is an error to use ``--concurrency=multiprocessing`` and
other run-affecting options on the command line. This prevents
failures like those reported in `issue 495`_.
- Filtering the HTML report is now faster, thanks to Ville Skyttä.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=51
- update to 3.7:
* Added the ``--debug`` switch to ``coverage run``. It accepts a list of
options indicating the type of internal activity to log to stderr.
* Running code with ``coverage run -m`` now behaves more like Python does,
setting sys.path properly, which fixes `issue 207`_ and `issue 242`_.
* Coverage can now run .pyc files directly, closing `issue 264`_.
Over 15 other bugfixes, see included CHANGELOG
OBS-URL: https://build.opensuse.org/request/show/204138
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=31
+ Line numbers in the HTML report line up better with the source lines, fixing
issue 197
+ When specifying a directory as the source= option, the directory itself no
longer needs to have a __init__.py file, though its subdirectories do, to
be considered as source files.
+ Files encoded as UTF-8 with a BOM are now properly handled, fixing
issue 179_.
+ Fixed more cases of non-Python files being reported as Python source, and
then not being able to parse them as Python. Closes issue 82 (again).
+ Fixed memory leaks under Python 3, thanks, Brett Cannon. Closes issue 147_.
+ Optimized .pyo files may not have been handled correctly, issue 195_.
+ Certain unusually named file paths could have been mangled during reporting,
issue 194_.
+ Try to do a better job of the impossible task of detecting when we can't
build the C extension, fixing issue 183_.
+ Testing is now done with tox
- Changes from version 3.5.2:
+ No changes since 3.5.2.b1
- Changes from version 3.5.2b1
+ The HTML report has slightly tweaked controls: the buttons at the top of
the page are color-coded to the source lines they affect.
+ Custom CSS can be applied to the HTML report by specifying a CSS file as
the extra_css configuration value in the [html] section.
+ Source files with custom encodings declared in a comment at the top are now
properly handled during reporting on Python 2. Python 3 always handled them
properly. This fixes issue 157_.
+ Backup files left behind by editors are no longer collected by the source=
option, fixing issue 168_.
+ If a file doesn't parse properly as Python, we don't report it as an error
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-coverage?expand=0&rev=20
