Revisions of python-coverage
buildservice-autocommit
accepted
request 577962
from
Tomáš Chvátal (scarabeus_iv)
(revision 70)
baserev update by copy to link target
Tomáš Chvátal (scarabeus_iv)
accepted
request 577785
from
Arun Persaud (apersaud)
(revision 69)
update to latest version
buildservice-autocommit
accepted
request 575271
from
Tomáš Chvátal (scarabeus_iv)
(revision 68)
baserev update by copy to link target
Tomáš Chvátal (scarabeus_iv)
accepted
request 575253
from
Arun Persaud (apersaud)
(revision 67)
update to latest version
buildservice-autocommit
accepted
request 542485
from
Factory Maintainer (factory-maintainer)
(revision 66)
baserev update by copy to link target
buildservice-autocommit
accepted
request 539602
from
Jan Matejek (matejcik)
(revision 65)
baserev update by copy to link target
Jan Matejek (matejcik)
committed
(revision 64)
- test presence of python2 (not just if it is skipped; two different things now, unfortunately)
Jan Matejek (matejcik)
accepted
request 539366
from
Arun Persaud (apersaud)
(revision 63)
update to latest version
buildservice-autocommit
accepted
request 531395
from
Jan Matejek (matejcik)
(revision 62)
baserev update by copy to link target
Jan Matejek (matejcik)
accepted
request 531380
from
Arun Persaud (apersaud)
(revision 61)
update to latest version
buildservice-autocommit
accepted
request 516178
from
Todd R (TheBlackCat)
(revision 60)
baserev update by copy to link target
Todd R (TheBlackCat)
accepted
request 516177
from
Todd R (TheBlackCat)
(revision 59)
- Handle cases where python2 is disabled (needed for SLE backports compatibility)
buildservice-autocommit
accepted
request 483388
from
Jan Matejek (matejcik)
(revision 58)
baserev update by copy to link target
Jan Matejek (matejcik)
committed
(revision 57)
Jan Matejek (matejcik)
committed
(revision 56)
- uninstall alternatives in %postun
buildservice-autocommit
accepted
request 479620
from
Jan Matejek (matejcik)
(revision 55)
baserev update by copy to link target
Jan Matejek (matejcik)
accepted
request 479281
from
Jan Matejek (matejcik)
(revision 54)
- 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.
buildservice-autocommit
accepted
request 451184
from
Dirk Mueller (dirkmueller)
(revision 53)
baserev update by copy to link target
Dirk Mueller (dirkmueller)
accepted
request 450363
from
Hans-Peter Jansen (frispete)
(revision 52)
- 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
Dirk Mueller (dirkmueller)
committed
(revision 51)
- update to 4.2: - 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ä.
Displaying revisions 61 - 80 of 130