summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2012-04-18 07:27:59 -0400
committerNed Batchelder <ned@nedbatchelder.com>2012-04-18 07:27:59 -0400
commit42f5efa9bc9e5ec2fd02f9cf6b95541a93fca632 (patch)
tree28baf3d41e7a89c1082a9b6e9138474a50a0124e /CHANGES.txt
parentac8cf1852de2837234dab8cc823127e70c48e55e (diff)
downloadpython-coveragepy-42f5efa9bc9e5ec2fd02f9cf6b95541a93fca632.tar.gz
Don't complain about files that can't be parsed as Python if they didn't seem like Python at all. #82.
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index 78d8175..5288103 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -12,6 +12,10 @@ Version 3.5.2b1
- Backup files left behind by editors are no longer collected by the source=
option, fixing `issue 168`_.
+- If a file doesn't parse properly as Python, we don't report it as an error
+ if the filename seems like maybe it wasn't meant to be Python. This is a
+ pragmatic fix for `issue 82`_.
+
- When running a module with ``coverage run -m <modulename>``, certain details
of the execution environment weren't the same as for
``python -m <modulename>``. This had the unfortunate side-effect of making
@@ -24,6 +28,7 @@ Version 3.5.2b1
- When installing into pypy, we no longer attempt (and fail) to compile
the C tracer function, closing `issue 166`_.
+.. _issue 82: https://bitbucket.org/ned/coveragepy/issue/82/tokenerror-when-generating-html-report
.. _issue 155: https://bitbucket.org/ned/coveragepy/issue/155/cant-use-coverage-run-m-unittest-discover
.. _issue 157: https://bitbucket.org/ned/coveragepy/issue/157/chokes-on-source-files-with-non-utf-8
.. _issue 166: https://bitbucket.org/ned/coveragepy/issue/166/dont-try-to-compile-c-extension-on-pypy