From c2a99c7880afbcf7557a895b6fe9fa6cb3d14356 Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Sun, 10 Mar 2013 10:30:07 -0400 Subject: Don't issue spurious warnings about the trace function changing. Fixes #164 --- CHANGES.txt | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'CHANGES.txt') 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 -- cgit v1.2.1