diff options
| -rw-r--r-- | doc/cmd.rst | 3 | ||||
| -rw-r--r-- | doc/trouble.rst | 15 |
2 files changed, 1 insertions, 17 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 diff --git a/doc/trouble.rst b/doc/trouble.rst index 8f260604..16483bb2 100644 --- a/doc/trouble.rst +++ b/doc/trouble.rst @@ -53,21 +53,6 @@ coverage.py from working properly: .. _issue 43: https://bitbucket.org/ned/coveragepy/issues/43/coverage-measurement-fails-on-code -Things that require --timid ---------------------------- - -Some packages interfere with coverage measurement, but you might be able to -make it work by using the ``--timid`` command-line switch, or the ``[run] -timid=True`` configuration option. - -* `DecoratorTools`_, or any package which uses it, notably `TurboGears`_. - DecoratorTools fiddles with the trace function. You will need to use - ``--timid``. - -.. _DecoratorTools: https://pypi.org/project/DecoratorTools/ -.. _TurboGears: http://turbogears.org/ - - Still having trouble? --------------------- |