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 | 23a8f9a5d8c0c04e03dbe919ccb41fc43660e492 (patch) | |
| tree | 017d1cdee4ae6a0c9b4afa93d0f21b29ece3983d | |
| parent | a2249a8b08e3aaacb1c80c8d1a2394ba2826e271 (diff) | |
| download | python-coveragepy-git-23a8f9a5d8c0c04e03dbe919ccb41fc43660e492.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 d48c74e0..316df0c1 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 |