diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2021-10-17 13:59:24 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2021-10-17 13:59:24 -0400 |
| commit | 43e1c64c22abfff5f229579936a44038ec608e76 (patch) | |
| tree | b3e37c1c393d2fa978e83cc6afedea94ae56775e | |
| parent | b76d2ccdfd085a2606e8ddc63e930b83c4ebcab5 (diff) | |
| download | python-coveragepy-git-43e1c64c22abfff5f229579936a44038ec608e76.tar.gz | |
docs: correct the description of 'debug sys' tracer details. #1157
| -rw-r--r-- | doc/faq.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/faq.rst b/doc/faq.rst index 0fce8903..6043b32b 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -90,8 +90,8 @@ 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. +``CTrace: available`` or ``CTracer: unavailable``. If it says unavailble, +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. |