summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2011-03-24 22:49:37 -0400
committerNed Batchelder <ned@nedbatchelder.com>2011-03-24 22:49:37 -0400
commit01ea68a1088fc1cdbdd586624ac695c5b697edeb (patch)
tree7b64f69deaeda1fa07c38bfdb64c7c4d8e879eb3 /CHANGES.txt
parent1f950ca6c4c1da6d5f2f37faeb0217e9ff273b75 (diff)
downloadpython-coveragepy-git-01ea68a1088fc1cdbdd586624ac695c5b697edeb.tar.gz
Incremental HTML generation. Some cleanup would be good.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index cd07ce78..bbf42f26 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -22,6 +22,10 @@ Version 3.5
- A little bit of Jython support: `coverage run` can now measure Jython
execution by adapting when $py.class files are traced. Thanks, Adi Roiban.
+- HTML reporting is now incremental: a record is kept of the data that
+ produced the HTML reports, and only files whose data has changed will
+ be generated. This should make most HTML reporting faster.
+
- Pathological code execution could disable the trace function behind our
backs, leading to incorrect code measurement. Now if this happens,
coverage.py will issue a warning, at least alerting you to the problem.