- 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
- 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