Revisions of python-coverage
Hans-Peter Jansen (frispete)
committed
(revision 7)
- Update to version 6.2 * Feature: Now the --concurrency setting can now have a list of values, so that threads and another lightweight threading package can be measured together, such as --concurrency=gevent,thread. Closes issue 1012 and issue 1082. * Fix: A module specified as the source setting is imported during startup, before the user program imports it. This could cause problems if the rest of the program isn't ready yet. For example, issue 1203 describes a Django setting that is accessed before settings have been configured. Now the early import is wrapped in a try/except so errors then don't stop execution. * Fix: A colon in a decorator expression would cause an exclusion to end too early, preventing the exclusion of the decorated function. This is now fixed. * Fix: The HTML report now will not overwrite a .gitignore file that already exists in the HTML output directory (follow-on for issue 1244). * API: The exceptions raised by Coverage.py have been specialized, to provide finer-grained catching of exceptions by third-party code. * API: Using suffix=False when constructing a Coverage object with multiprocessing wouldn't suppress the data file suffix (issue 989). This is now fixed. * Debug: The coverage debug data command will now sniff out combinable data files, and report on all of them. * Debug: The coverage debug command used to accept a number of topics at a time, and show all of them, though this was never documented. This no longer works, to allow for command-line options in the future. - Release notes for 6.1.2
Hans-Peter Jansen (frispete)
committed
(revision 6)
- Skip Py2 build
Hans-Peter Jansen (frispete)
committed
(revision 5)
touch
Hans-Peter Jansen (frispete)
committed
(revision 4)
touch
buildservice-autocommit
accepted
request 450363
from
Hans-Peter Jansen (frispete)
(revision 3)
auto commit by copy to link target
Hans-Peter Jansen (frispete)
committed
(revision 2)
------------------------------------------------------------------- Sat Jan 14 19:28:37 UTC 2017 - hpj@urpla.net - 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.
Hans-Peter Jansen (frispete)
committed
(revision 1)
Displaying all 7 revisions