summaryrefslogtreecommitdiff
path: root/doc/cmd.rst
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2009-08-09 18:12:23 -0400
committerNed Batchelder <ned@nedbatchelder.com>2009-08-09 18:12:23 -0400
commitcba5899f0bad8a49b17750df58ddd532975c1062 (patch)
tree02eac123c89f439b440c7efb6a7aa0a98bd12e80 /doc/cmd.rst
parentb159081bb7df0c838bcf01ca9e70899a61ae9d9b (diff)
downloadpython-coveragepy-git-cba5899f0bad8a49b17750df58ddd532975c1062.tar.gz
Fix a problem with DecoratorTools fiddling with the trace function and screwing us up. Now the Python trace function is simpler, with no variability of registered trace function. Fixes bugs #12 and #13.
Diffstat (limited to 'doc/cmd.rst')
-rw-r--r--doc/cmd.rst6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst
index 2f8ec170..ae7282f8 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -57,6 +57,12 @@ Arguments after your file name are passed to your program in sys.argv.
By default, coverage does not measure code installed with the Python interpreter.
If you want to measure that code as well as your own, add the -L flag.
+If your coverage results seems 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 set
+with the environment variable COVERAGE_OPTIONS set to '--timid'.
+
Combining data files
--------------------