summaryrefslogtreecommitdiff
path: root/doc/faq.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2016-10-02 11:03:33 -0400
committerNed Batchelder <ned@nedbatchelder.com>2016-10-02 11:03:33 -0400
commitf241ca6050ffc5e3d285b1af290b69f38e3eb21b (patch)
tree7c7a0561f0c9b4574adddc730fc5e094dde66a24 /doc/faq.rst
parentb0c8d08d9d1bd16720113898690f4bc99c8288e9 (diff)
downloadpython-coveragepy-git-f241ca6050ffc5e3d285b1af290b69f38e3eb21b.tar.gz
Use doc8 for some light checking of doc files
Diffstat (limited to 'doc/faq.rst')
-rw-r--r--doc/faq.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/faq.rst b/doc/faq.rst
index d10e14dd..11261f7d 100644
--- a/doc/faq.rst
+++ b/doc/faq.rst
@@ -58,9 +58,9 @@ coverage.start() before importing the modules that define your functions.
Make sure you are using the C trace function. Coverage.py provides two
implementations of the trace function. The C implementation runs much faster.
To see what you are running, use ``coverage debug sys``. The output contains
-details of the environment, including a line that says either ``tracer: CTracer``
-or ``tracer: PyTracer``. If it says ``PyTracer`` then you are using the
-slow Python implementation.
+details of the environment, including a line that says either
+``tracer: CTracer`` or ``tracer: PyTracer``. If it says ``PyTracer`` then you
+are using the slow Python implementation.
Try re-installing coverage.py to see what happened and if you get the CTracer
as you should.