sources that do not end with .py\w? are ignored #425

close #425

--HG--
branch : issue-425

2 files changed, 4 insertions, 3 deletions

diff --git a/doc/cmd.rst b/doc/cmd.rst
index bbeff182..faa0048d 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -93,7 +93,7 @@ If you want :ref:`branch coverage <branch>` measurement, use the ``--branch``
 flag.  Otherwise only statement coverage is measured.
 
 You can specify the code to measure with the ``--source``, ``--include``, and
-``--omit`` switches.  See :ref:`Specifying source files <source_execution>` for
+``--omit`` switches.  See :ref:`Specifying source directories <source_execution>` for
 details of their interpretation.  Remember to put options for run after "run",
 but before the program invocation::
 
diff --git a/doc/source.rst b/doc/source.rst
index 8f5b31bc..8d831c44 100644
--- a/doc/source.rst
+++ b/doc/source.rst
@@ -35,9 +35,10 @@ source inside these directories or packages will be measured.  Specifying the
 source option also enables coverage.py to report on unexecuted files, since it
 can search the source tree for files that haven't been measured at all.  Only
 importable files (ones at the root of the tree, or in directories with a
-``__init__.py`` file) will be considered, and files with unusual punctuation in
+``__init__.py`` file) will be considered. Files with unusual punctuation in
 their names will be skipped (they are assumed to be scratch files written by
-text editors).
+text editors). Files that do not end with ``.py`` or ``.pyo`` or ``.pyc``
+will also be skipped.
 
 You can further fine-tune coverage.py's attention with the ``--include`` and
 ``--omit`` switches (or ``[run] include`` and ``[run] omit`` configuration