summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2013-03-10 10:30:07 -0400
committerNed Batchelder <ned@nedbatchelder.com>2013-03-10 10:30:07 -0400
commitc2a99c7880afbcf7557a895b6fe9fa6cb3d14356 (patch)
treed36bffd7e2d877915c464fe1b03bc9d3e701d290 /CHANGES.txt
parentfa53c8a6abd4407a486c5d54c7ad760ea3126a95 (diff)
downloadpython-coveragepy-c2a99c7880afbcf7557a895b6fe9fa6cb3d14356.tar.gz
Don't issue spurious warnings about the trace function changing. Fixes #164
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 200204d..82b1b84 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -7,6 +7,11 @@ Change history for Coverage.py
- Improved the branch coverage mechanism, fixing `issue 175`_.
+- 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