diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2011-10-31 07:22:23 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2011-10-31 07:22:23 -0400 |
| commit | f4e26c75e38c03f94cd2c74949f6f58c42b4f86b (patch) | |
| tree | 81ca8c8ce9e424b9e6446a8c6d096b53423d0e89 | |
| parent | bb50b8d5c6c50feb676bb5b5f6aecc247c94d7c5 (diff) | |
| download | python-coveragepy-f4e26c75e38c03f94cd2c74949f6f58c42b4f86b.tar.gz | |
#155 is fixed.
| -rw-r--r-- | CHANGES.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 1caa7ba..66bf5c8 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -2,6 +2,17 @@ Change history for Coverage.py ------------------------------ +Version 3.5.2b1 +--------------- + +- When running a module with ``coverage run -m <modulename>``, certain details + of the execution environment weren't the same as for + ``python -m <modulename>``. This had the unfortunate side-effect of making + ``coverage run -m unittest discover`` not work if you had tests in a + directory named "test". This fixes `issue 155`_. + +.. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover + Version 3.5.1 --- 23 September 2011 ----------------------------------- |