diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2017-01-14 10:49:05 -0500 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2017-01-14 10:49:05 -0500 |
| commit | 51e00501ae3d12e019e5dc86f99f93786c8ee2d5 (patch) | |
| tree | 05a5c0151545124b36a744d928348820495ebe88 | |
| parent | 549bad2d676f03c18cfb3b8ed5392bab5eae2ad3 (diff) | |
| download | python-coveragepy-git-51e00501ae3d12e019e5dc86f99f93786c8ee2d5.tar.gz | |
Mark #322 as fixed
| -rw-r--r-- | CHANGES.rst | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/CHANGES.rst b/CHANGES.rst index 3a1c25d3..886cc6d8 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -23,7 +23,9 @@ Unreleased - Previously, coverage.py couldn't start on Jython, due to that implementation missing the multiprocessing module (`issue 551`_). This problem has now been - fixed. + 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 @@ -31,6 +33,7 @@ Unreleased coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. +.. _issue 322: https://bitbucket.org/ned/coveragepy/issues/322/cannot-use-coverage-with-jython .. _issue 549: https://bitbucket.org/ned/coveragepy/issues/549/skip-covered-with-100-coverage-throws-a-no .. _issue 551: https://bitbucket.org/ned/coveragepy/issues/551/coveragepy-cannot-be-imported-in-jython27 |