diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-27 09:18:36 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2013-04-27 09:18:36 -0400 |
| commit | fb8cc16d50ea9eede83c729c542fa52026974f3b (patch) | |
| tree | 05e4d7278d75b67c1367f7674cb2a4204392aee6 | |
| parent | 3ac2bd704a83c7c2e7a2b27d9033eab8596c03b4 (diff) | |
| download | python-coveragepy-fb8cc16d50ea9eede83c729c542fa52026974f3b.tar.gz | |
Keep the paperwork up to date.
| -rw-r--r-- | CHANGES.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CHANGES.txt b/CHANGES.txt index d48c74e..316df0c 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -16,7 +16,7 @@ Change history for Coverage.py - 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. + changed, measurement is likely wrong: None." This fixes `issue 164`_. .. _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 |