diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2010-11-06 16:49:23 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2010-11-06 16:49:23 -0400 |
| commit | 3f1b714b7e767573b99fa167e62fa291738bf4e4 (patch) | |
| tree | 10240229c367701d67053d93332e703a59e07367 /CHANGES.txt | |
| parent | bd9091d4b1217d6ad5271e1c6540045e22e33d21 (diff) | |
| download | python-coveragepy-git-3f1b714b7e767573b99fa167e62fa291738bf4e4.tar.gz | |
Detect when our trace function is yanked out from under us, and warn the user. Finishes, but does not fix, issue #93.
Diffstat (limited to 'CHANGES.txt')
| -rw-r--r-- | CHANGES.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index 4604489f..3c04d3b3 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -9,6 +9,13 @@ Version 3.5 - A little bit of Jython support: `coverage run` can now measure Jython execution by adapting when $py.class files are traced. Thanks, Adi Roiban. +- Pathological code execution could disable the trace function behind our + backs, leading to incorrect code measurement. Now if this happens, + coverage.py will issue a warning, at least alerting you to the problem. + Closes `issue 93`_. Thanks to Marius Gedminas for the idea. + +.. _issue 93: http://bitbucket.org/ned/coveragepy/issue/93/copying-a-mock-object-breaks-coverage + Version 3.4 --- 19 September 2010 --------------------------------- |