diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-22 07:56:17 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-22 07:56:17 -0400 |
| commit | dfe6463e39906d3f1ea38557e64a4fd0287b0f15 (patch) | |
| tree | 4c1317a99cb26b34e7fbfb6a46264abba25ba735 /CHANGES.txt | |
| parent | dc57e1a9e3188e88df88ea48c5d725be8ab21f52 (diff) | |
| download | python-coveragepy-dfe6463e39906d3f1ea38557e64a4fd0287b0f15.tar.gz | |
Turns out issue #142 was fixed a long time ago.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 48876c1..d48c74e 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -253,7 +253,7 @@ Version 3.5.2b1 --- 29 April 2012 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`_. + directory named "test". This fixes `issue 155`_ and `issue 142`_. - Now the exit status of your product code is properly used as the process status when running ``python -m coverage run ...``. Thanks, JT Olds. @@ -262,6 +262,7 @@ Version 3.5.2b1 --- 29 April 2012 the C tracer function, closing `issue 166`_. .. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report +.. _issue 142: https://bitbucket.org/ned/coveragepy/issue/142/executing-python-file-syspath-is-replaced .. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover .. _issue 157: https://bitbucket.org/ned/coveragepy/issue/157/chokes-on-source-files-with-non-utf-8 .. _issue 166: https://bitbucket.org/ned/coveragepy/issue/166/dont-try-to-compile-c-extension-on-pypy |