diff options
author | Ned Batchelder <ned@nedbatchelder.com> | 2017-10-24 07:17:11 -0400 |
---|---|---|
committer | Ned Batchelder <ned@nedbatchelder.com> | 2017-10-24 07:17:11 -0400 |
commit | 26821ed8e6ea20925ab859bf5e06607f0861bb4c (patch) | |
tree | f5f705f292da442b0195fd05eb5e2dd1f9d35c28 /doc | |
parent | 0884bfddabbe7c1b7f9a97c15e20c1d08b3ec05c (diff) | |
download | python-coveragepy-26821ed8e6ea20925ab859bf5e06607f0861bb4c.tar.gz |
Add the latest warning to the docs, and give them consistent punctuation
Diffstat (limited to 'doc')
-rw-r--r-- | doc/cmd.rst | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst index dc70353..8dbe56e 100644 --- a/doc/cmd.rst +++ b/doc/cmd.rst @@ -165,12 +165,18 @@ could affect the measurement process. The possible warnings include: This could be because you asked to measure only modules that never ran, or for other reasons. -* "Module XXX was previously imported, but not measured. (module-not-measured)" +* "Module XXX was previously imported, but not measured (module-not-measured)" You asked coverage.py to measure module XXX, but it had already been imported when coverage started. This meant coverage.py couldn't monitor its execution. +* "--include is ignored because --source is set (include-ignored)" + + Both ``--include`` and ``--source`` were specified while running code. Both + are meant to focus measurement on a particular part of your source code, so + ``--include`` is ignored in favor of ``--source``. + Individual warnings can be disabled with the `disable_warnings <config_run_disable_warnings>`_ configuration setting. To silence "No data was collected," add this to your .coveragerc file:: |