diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2018-09-21 08:44:56 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2018-09-21 08:44:56 -0400 |
| commit | 21a9e672336675aa4ad55b3fb946661b6e5616f2 (patch) | |
| tree | 216ead72f308b5ad55fdb89c05809f1a50ce67a0 /doc/cmd.rst | |
| parent | b4b9c0b458325c98a3b3a3fcb6b3daa5bb63f4ec (diff) | |
| download | python-coveragepy-git-21a9e672336675aa4ad55b3fb946661b6e5616f2.tar.gz | |
Turbogears is not worth a mention
Diffstat (limited to 'doc/cmd.rst')
| -rw-r--r-- | doc/cmd.rst | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst index 908b2ee9..c0b91221 100644 --- a/doc/cmd.rst +++ b/doc/cmd.rst @@ -124,8 +124,7 @@ code as well as your own, add the ``-L`` (or ``--pylib``) flag. 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. Projects that use DecoratorTools, including -TurboGears, will need to use ``--timid`` to get correct results. +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 |