summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2013-10-05 21:19:10 -0400
committerNed Batchelder <ned@nedbatchelder.com>2013-10-05 21:19:10 -0400
commit7a28bb348801a9569ee86e0dbcefc49ef3bc14eb (patch)
treebe9bcededc55a33bbc05a309de954991629a2973 /CHANGES.txt
parent9bb2dc364c54ee72d02993f534532fce524bcdef (diff)
downloadpython-coveragepy-git-7a28bb348801a9569ee86e0dbcefc49ef3bc14eb.tar.gz
Go to 3.7
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index c7e25b28..bf54d751 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -2,8 +2,8 @@
Change history for Coverage.py
------------------------------
-3.6.1
------
+3.7b1 --- 6 October 2013
+------------------------
- Added the ``--debug`` switch to ``coverage run``. It accepts a list of
options indicating the type of internal activity to log to stderr.
@@ -28,8 +28,8 @@ Change history for Coverage.py
``~build/src``, for example), and with environment variable expansion
(``build/$BUILDNUM/src``).
-- Trying to create an XML report with the nose plugin, but no files to report
- on, would cause a ZeroDivideError, but no longer does, fixing `issue 250`_.
+- Trying to create an XML report with no files to report on, would cause a
+ ZeroDivideError, but no longer does, fixing `issue 250`_.
- When running a threaded program under the Python tracer, coverage no longer
issues a spurious warning about the trace function changing: "Trace function