diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-20 19:10:51 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-20 19:10:51 -0400 |
| commit | b33f839a07a6ad36464330d98822bc0341c4858f (patch) | |
| tree | 75cc4ca73e2830adef784700860812416c7460cc /CHANGES.txt | |
| parent | 65586d18d36f28da6bdf99aada5d821cc6b2846d (diff) | |
| download | python-coveragepy-b33f839a07a6ad36464330d98822bc0341c4858f.tar.gz | |
Get sys.path right when running modules with -m, fixes #207 and #242.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 82b1b84..0f49740 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -7,13 +7,17 @@ Change history for Coverage.py - Improved the branch coverage mechanism, fixing `issue 175`_. +- Running code with ``coverage run -m`` now behaves more like Python does, + setting sys.path properly, which fixes `issue 207`_ and `issue 242`. + - When running a threaded program under the Python tracer, coverage would issue a spurious warning about the trace function changing: "Trace function changed, measurement is likely wrong: None." This is now fixed. .. _issue 164: https://bitbucket.org/ned/coveragepy/issue/164/trace-function-changed-warning-when-using .. _issue 175: https://bitbucket.org/ned/coveragepy/issue/175/branch-coverage-gets-confused-in-certain - +.. _issue 207: https://bitbucket.org/ned/coveragepy/issue/207/run-m-cannot-find-module-or-package-in +.. _issue 242: https://bitbucket.org/ned/coveragepy/issue/242/running-a-two-level-package-doesnt-work Version 3.6 --- 5 January 2013 ------------------------------ |