summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2018-09-21 08:47:36 -0400
committerNed Batchelder <ned@nedbatchelder.com>2018-09-21 08:47:36 -0400
commit85f63fef4d3b8e1b1328e3268c3eee3900e1d8a4 (patch)
tree6afe0df5432489d9637f39ed4c2ff312441d897f /doc
parent21a9e672336675aa4ad55b3fb946661b6e5616f2 (diff)
downloadpython-coveragepy-git-85f63fef4d3b8e1b1328e3268c3eee3900e1d8a4.tar.gz
Put these paragraphs in a more reasonable order
Diffstat (limited to 'doc')
-rw-r--r--doc/cmd.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst
index c0b91221..00a9a6c3 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -118,6 +118,10 @@ configuration file for all options.
.. _gevent: http://www.gevent.org/
.. _eventlet: http://eventlet.net/
+If you are measuring coverage in a multi-process program, or across a number of
+machines, you'll want the ``--parallel-mode`` switch to keep the data separate
+during measurement. See :ref:`cmd_combining` below.
+
By default, coverage.py does not measure code installed with the Python
interpreter, for example, the standard library. If you want to measure that
code as well as your own, add the ``-L`` (or ``--pylib``) flag.
@@ -126,10 +130,6 @@ If your coverage results seem to be overlooking code that you know has been
executed, try running coverage.py again with the ``--timid`` flag. This uses a
simpler but slower trace method, and might be needed in rare cases.
-If you are measuring coverage in a multi-process program, or across a number of
-machines, you'll want the ``--parallel-mode`` switch to keep the data separate
-during measurement. See :ref:`cmd_combining` below.
-
.. _cmd_warnings: