summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2012-11-19 22:51:06 -0500
committerNed Batchelder <ned@nedbatchelder.com>2012-11-19 22:51:06 -0500
commitbbf1219c55cc39701e02dae4324210ef9c6928c3 (patch)
tree60fdbd12b31bb0131305804aeee3b9e88390c112
parent0be9de1ff6b6a852849d31fedfb41b94bec63267 (diff)
downloadpython-coveragepy-bbf1219c55cc39701e02dae4324210ef9c6928c3.tar.gz
Tweak the wording.
-rw-r--r--CHANGES.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 695b415..c19421e 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -27,10 +27,11 @@ Version 3.6b1
- Embarrassingly, the `[xml] output=' setting in the .coveragerc file simply
didn't work. Now it does.
-- Coverage percentage metrics are computed slightly differently under branch
- coverage. This means that completely unexecuted files will now correctly
- have 0% coverage, fixing `issue 156`_. This also means that your total
- coverage numbers will be lower in general if you are using branch coverage.
+- Coverage percentage metrics are now computed slightly differently under
+ branch coverage. This means that completely unexecuted files will now
+ correctly have 0% coverage, fixing `issue 156`_. This also means that your
+ total coverage numbers will generally now be lower if you are measuring
+ branch coverage.
- When installing, now in addition to creating a "coverage" command, two new
aliases are also installed. A "coverage2" or "coverage3" command will be