summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2010-09-06 13:51:07 -0400
committerNed Batchelder <ned@nedbatchelder.com>2010-09-06 13:51:07 -0400
commitde467542b5638e3f5fb621789328d29c39cfddc9 (patch)
tree55ae6b9035b67c43df7dc70603536c0e47fe2baf
parenta6621b2ceaf4d0b72456903749ca1f6247a972fc (diff)
downloadpython-coveragepy-git-de467542b5638e3f5fb621789328d29c39cfddc9.tar.gz
Doc tweaks for 3.4b2
-rw-r--r--CHANGES.txt7
-rw-r--r--doc/changes.rst36
-rw-r--r--doc/conf.py2
-rw-r--r--doc/index.rst8
-rw-r--r--doc/install.rst5
-rw-r--r--setup.py3
6 files changed, 43 insertions, 18 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 2529ef27..5c2809b8 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,8 +3,8 @@ Change history for Coverage.py
------------------------------
-Version 3.4b2
--------------
+Version 3.4b2 --- 6 September 2010
+----------------------------------
- Completely unexecuted files can now be included in coverage results, reported
as 0% covered. This only happens if the --source option is specified, since
@@ -19,8 +19,7 @@ Version 3.4b2
are rounded otherwise. Fixes `issue 41`_ and `issue 70`_.
- The precision of reported coverage percentages can be set with the
- ``[report] precision`` config file setting. Default is still 0. Completes
- `issue 16`_.
+ ``[report] precision`` config file setting. Completes `issue 16`_.
- Threads derived from ``threading.Thread`` with an overridden `run` method
would report no coverage for the `run` method. This is now fixed, closing
diff --git a/doc/changes.rst b/doc/changes.rst
index 9fbf159a..832ae1dc 100644
--- a/doc/changes.rst
+++ b/doc/changes.rst
@@ -13,8 +13,8 @@ Major change history for coverage.py
:history: 20100221T151900, changes for 3.3
:history: 20100306T181400, changes for 3.3.1
:history: 20100725T211700, updated for 3.4.
-:history: 20100820T151500, updated for 3.4beta1.
-
+:history: 20100820T151500, updated for 3.4b1
+:history: 20100906T133800, updated for 3.4b2
These are the major changes for coverage.py. For a more complete change
history, see the `CHANGES.txt`_ file in the source tree.
@@ -22,8 +22,8 @@ history, see the `CHANGES.txt`_ file in the source tree.
.. _CHANGES.txt: http://bitbucket.org/ned/coveragepy/src/tip/CHANGES.txt
-Version 3.4 beta --- 21 August 2010
------------------------------------
+Version 3.4 beta --- 6 September 2010
+-------------------------------------
- BACKWARD INCOMPATIBILITY: the ``--omit`` and ``--include`` switches now take
file patterns rather than file prefixes, closing `issue 34`_ and `issue 36`_.
@@ -38,6 +38,10 @@ Version 3.4 beta --- 21 August 2010
to control what modules it measures. This can speed execution and reduce the
amount of data during reporting. Thanks Zooko.
+- Completely unexecuted files can now be included in coverage results, reported
+ as 0% covered. This only happens if the --source option is specified, since
+ coverage.py needs guidance about where to look for source files.
+
- Various warnings are printed to stderr for problems encountered during data
measurement: if a ``--source`` module has no Python source to measure, or is
never encountered at all, or if no data is collected.
@@ -54,6 +58,21 @@ Version 3.4 beta --- 21 August 2010
rather than increasing the executed lines to varying targets. Once
suggested, this seemed blindingly obvious.
+- Coverage percentages are now displayed uniformly across reporting methods.
+ Previously, different reports could round percentages differently. Also,
+ percentages are only reported as 0% or 100% if they are truly 0 or 100, and
+ are rounded otherwise. Fixes `issue 41`_ and `issue 70`_.
+
+- The XML report output now properly includes a percentage for branch coverage,
+ fixing `issue 65`_ and `issue 81`_.
+
+- The precision of reported coverage percentages can be set with the
+ ``[report] precision`` config file setting. Completes `issue 16`_.
+
+- Threads derived from ``threading.Thread`` with an overridden `run` method
+ would report no coverage for the `run` method. This is now fixed, closing
+ `issue 85`_.
+
- Line numbers in HTML source pages are clickable, linking directly to that
line, which is highlighted on arrival. Added a link back to the index page
at the bottom of each HTML page.
@@ -69,12 +88,17 @@ Version 3.4 beta --- 21 August 2010
can't be reported anyway. Fixes `issue 52`_ and `issue 61`_.
.. _issue 1: http://bitbucket.org/ned/coveragepy/issue/1/empty-__init__py-files-are-reported-as-1-executable
+.. _issue 16: http://bitbucket.org/ned/coveragepy/issue/16/allow-configuration-of-accuracy-of-percentage-totals
.. _issue 34: http://bitbucket.org/ned/coveragepy/issue/34/enhanced-omit-globbing-handling
.. _issue 36: http://bitbucket.org/ned/coveragepy/issue/36/provide-regex-style-omit
+.. _issue 41: http://bitbucket.org/ned/coveragepy/issue/41/report-says-100-when-it-isnt-quite-there
.. _issue 52: http://bitbucket.org/ned/coveragepy/issue/52/doctesttestfile-confuses-source-detection
-.. _issue 56: http://bitbucket.org/ned/coveragepy/issue/56
+.. _issue 56: http://bitbucket.org/ned/coveragepy/issue/56/coveragepy-cant-trace-child-processes-of-a
.. _issue 61: http://bitbucket.org/ned/coveragepy/issue/61/annotate-i-doesnt-work
-
+.. _issue 65: http://bitbucket.org/ned/coveragepy/issue/65/branch-option-not-reported-in-cobertura
+.. _issue 70: http://bitbucket.org/ned/coveragepy/issue/70/text-report-and-html-report-disagree-on-coverage
+.. _issue 81: http://bitbucket.org/ned/coveragepy/issue/81/xml-report-does-not-have-condition-coverage-attribute-for-lines-with-a
+.. _issue 85: http://bitbucket.org/ned/coveragepy/issue/85/threadrun-isnt-measured
Version 3.3.1 --- 6 March 2010
------------------------------
diff --git a/doc/conf.py b/doc/conf.py
index ddd26253..9e2aabcb 100644
--- a/doc/conf.py
+++ b/doc/conf.py
@@ -49,7 +49,7 @@ copyright = u'2009-2010, Ned Batchelder'
# The short X.Y version.
version = '3.4'
# The full version, including alpha/beta/rc tags.
-release = '3.4 beta 1'
+release = '3.4 beta 2'
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
diff --git a/doc/index.rst b/doc/index.rst
index 1d5fea63..5594318c 100644
--- a/doc/index.rst
+++ b/doc/index.rst
@@ -13,8 +13,8 @@ coverage.py
:history: 20100224T204700, version 3.3
:history: 20100306T181500, version 3.3.1
:history: 20100725T211700, updated for 3.4.
-:history: 20100820T151500, updated for 3.4beta1.
-
+:history: 20100820T151500, updated for 3.4b1.
+:history: 20100906T134700, updated for 3.4b2.
Coverage.py is a tool for measuring code coverage of Python programs. It
monitors your program, noting which parts of the code have been executed, then
@@ -24,8 +24,8 @@ Coverage measurement is typically used to gauge the effectiveness of tests. It
can show which parts of your code are being exercised by tests, and which are
not.
-The latest version is 3.4, in beta.
-It is supported on Python 2.3 through 3.2 alpha.
+The latest version is 3.4 beta 2, release 6 September 2010.
+It is supported on Python 2.3 through 3.2 alpha 2.
Quick start
diff --git a/doc/install.rst b/doc/install.rst
index 90c621fa..5db27636 100644
--- a/doc/install.rst
+++ b/doc/install.rst
@@ -5,7 +5,8 @@ Installation
============
:history: 20100725T225600, new for 3.4.
-:history: 20100820T151500, updated for 3.4beta1.
+:history: 20100820T151500, updated for 3.4b1.
+:history: 20100906T134800, updated for 3.4b2.
.. highlight:: console
.. _coverage_pypi: http://pypi.python.org/pypi/coverage
@@ -57,4 +58,4 @@ If all went well, you should be able to open a command prompt, and see
coverage installed properly::
$ coverage --version
- Coverage.py, version 3.4b1. http://nedbatchelder.com/code/coverage/3.4b1
+ Coverage.py, version 3.4b2. http://nedbatchelder.com/code/coverage/3.4b2
diff --git a/setup.py b/setup.py
index 23762f2c..73891430 100644
--- a/setup.py
+++ b/setup.py
@@ -15,7 +15,8 @@ New in 3.2: Branch coverage!
New in 3.3: .coveragerc files.
-New in 3.4: Better control over source to measure.
+New in 3.4: Better control over source to measure, and unexecuted files
+can be reported.
"""
# This file is used unchanged under all versions of Python, 2.x and 3.x.