diff options
| author | Charles Chan <charleswhchan@users.noreply.github.com> | 2023-05-05 18:12:09 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-05 18:12:09 -0700 |
| commit | 4cbe7f8514a0f7d4a7a2dbf21371476410ddf23d (patch) | |
| tree | 21b06109c5eb6ec3bd491c25dabe55df6c840e47 | |
| parent | cf3602ffa7396d8f784c1a1e814ff24c6c31f793 (diff) | |
| download | python-coveragepy-git-4cbe7f8514a0f7d4a7a2dbf21371476410ddf23d.tar.gz | |
docs: fix typo in faq.rst (#1619)
CTrace --> CTracer
| -rw-r--r-- | doc/faq.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/faq.rst b/doc/faq.rst index b25dce0f..d4f5a565 100644 --- a/doc/faq.rst +++ b/doc/faq.rst @@ -121,7 +121,7 @@ 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 -``CTrace: available`` or ``CTracer: unavailable``. If it says unavailable, +``CTracer: available`` or ``CTracer: unavailable``. If it says unavailable, then you are using the slow Python implementation. Try re-installing coverage.py to see what happened and if you get the CTracer |