summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2011-05-28 19:01:28 -0400
committerNed Batchelder <ned@nedbatchelder.com>2011-05-28 19:01:28 -0400
commitadde2749360d445328405b9a5197960df181b3ad (patch)
treeadc015b5fa49f57c1d712c3f2a75f9f635e056c4
parent8f7bf68908351fbe790f4778307368bbf1adc455 (diff)
downloadpython-coveragepy-git-adde2749360d445328405b9a5197960df181b3ad.tar.gz
Minor cleanups
-rw-r--r--CHANGES.txt15
-rw-r--r--coverage/results.py4
2 files changed, 11 insertions, 8 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index a4ce47c3..eda712ed 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -3,8 +3,8 @@ Change history for Coverage.py
------------------------------
-Version 3.5
------------
+Version 3.5b1
+-------------
- The HTML report now has hotkeys. Try ``n``, ``s``, ``m``, ``x``, ``b``,
``p``, and ``c`` on the overview page to change the column sorting.
@@ -25,13 +25,10 @@ Version 3.5
- Modules can now be run directly using ``coverage run -m modulename``, to
mirror Python's ``-m`` flag. Closes `issue 95`_, thanks, Brandon Rhodes.
-- ``coverage run`` didn't emulate Python accurately in one detail: the
+- ``coverage run`` didn't emulate Python accurately in one small detail: the
current directory inserted into ``sys.path`` was relative rather than
absolute. This is now fixed.
-- 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.
@@ -59,6 +56,11 @@ Version 3.5
the directory name to python: ``python coverage_py_working_dir run ...``.
Thanks, Brett Cannon.
+- A little bit of Jython support: `coverage run` can now measure Jython
+ execution by adapting when $py.class files are traced. Thanks, Adi Roiban.
+ Jython still doesn't provide the Python libraries needed to make
+ coverage reporting work, unfortunately.
+
- Internally, files are now closed explicitly, fixing `issue 104`_. Thanks,
Brett Cannon.
@@ -72,6 +74,7 @@ Version 3.5
.. _issue 123: https://bitbucket.org/ned/coveragepy/issue/123/pyeval_settrace-used-in-way-that-breaks
.. _issue 125: https://bitbucket.org/ned/coveragepy/issue/125/coverage-removes-decoratortoolss-tracing
+
Version 3.4 --- 19 September 2010
---------------------------------
diff --git a/coverage/results.py b/coverage/results.py
index d92b503c..7b032f18 100644
--- a/coverage/results.py
+++ b/coverage/results.py
@@ -97,8 +97,8 @@ class Analysis(object):
# trouble, and here is where it's the least burden to remove them.
unpredicted = [
e for e in executed
- if e not in possible
- and e[0] != e[1]
+ if e not in possible
+ and e[0] != e[1]
and e[0] not in self.no_branch
]
return sorted(unpredicted)