diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2014-09-28 18:42:30 -0400 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2014-09-28 18:42:30 -0400 |
| commit | d33fe1f90216e24039d5cbd003219543d1671313 (patch) | |
| tree | bbde25cd2c22e8245e0270f656f3180250a7bfb4 /doc | |
| parent | 5de5ff656824bc985f0a31156ffb8e076d178e46 (diff) | |
| download | python-coveragepy-git-d33fe1f90216e24039d5cbd003219543d1671313.tar.gz | |
Remove support for COVERAGE_OPTIONS environment variable.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/cmd.rst | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst index 96c27634..cd6ae955 100644 --- a/doc/cmd.rst +++ b/doc/cmd.rst @@ -113,9 +113,7 @@ code as well as your own, add the ``-L`` flag. If your coverage results seem to be overlooking code that you know has been executed, try running coverage 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. This option -can also be enabled by setting the environment variable COVERAGE_OPTIONS to -``--timid``. +TurboGears, will need to use ``--timid`` to get correct results. 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 |