Don't trace any files with names starting with less-than. They are all fake, and can't be reported on anyway. Fixes #61.

2 files changed, 9 insertions, 3 deletions

diff --git a/CHANGES.txt b/CHANGES.txt
index 4cdbeffb..ccec2066 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -19,6 +19,9 @@ Next version
   and parent processes.  Use ``coverage run -p`` to get two data files that can
   be combined with ``coverage combine``.  Fixes `issue 56`_.
 
+- Doctest text files are no longer recorded in the coverage data, since they
+  can't be reported anyway.  Fixes `issue 61`_.
+
 - Source files can have more than one dot in them (foo.test.py), and will be
   treated properly while reporting.  Fixes `issue 46`_.
 
@@ -31,6 +34,7 @@ Next version
 .. _issue 46: http://bitbucket.org/ned/coveragepy/issue/46
 .. _issue 53: http://bitbucket.org/ned/coveragepy/issue/53
 .. _issue 56: http://bitbucket.org/ned/coveragepy/issue/56
+.. _issue 61: http://bitbucket.org/ned/coveragepy/issue/61
 .. _issue 62: http://bitbucket.org/ned/coveragepy/issue/62
 
 
diff --git a/coverage/control.py b/coverage/control.py
index a3287ae6..e4f5fae7 100644
--- a/coverage/control.py
+++ b/coverage/control.py
@@ -139,9 +139,11 @@ class coverage(object):
         should not.
 
         """
-        if filename == '<string>':
-            # There's no point in ever tracing string executions, we can't do
-            # anything with the data later anyway.
+        if filename[0] == '<':
+            # Lots of non-file execution is represented with artificial
+            # filenames like "<string>", "<doctest readme.txt[0]>", or
+            # "<exec_function>".  Don't ever trace these executions, since we
+            # can't do anything with the data later anyway.
             return False
 
         # Compiled Python files have two filenames: frame.f_code.co_filename is