Message246834
While working on #24644, I noticed that the help for python -mtrace is quite wrong.
$ python -mtrace --help
Usage: /usr/lib/python3.4/trace.py [OPTIONS] <file> [ARGS]
Meta-options:
--help Display this help then exit.
--version Output version information then exit.
Otherwise, exactly one of the following three options must be given:
-t, --trace Print each line to sys.stdout before it is executed.
-c, --count Count the number of times each line is executed
and write the counts to <module>.cover for each
module executed, in the module's directory.
See also `--coverdir', `--file', `--no-report' below.
-l, --listfuncs Keep track of which functions are executed at least
once and write the results to sys.stdout after the
program exits.
-T, --trackcalls Keep track of caller/called pairs and write the
results to sys.stdout after the program exits.
-r, --report Generate a report from a counts file; do not execute
any code. `--file' must specify the results file to
read, which must have been created in a previous run
with `--count --file=FILE'.
<elided modifier flags>
1. Obviously, there are more than 3 options there.
2. Simple testing suggests that it is at least possible to pass both -t and -c simultaneously. I haven't tested other combinations. |
|
Date |
User |
Action |
Args |
2015-07-16 22:43:05 | Antony.Lee | set | recipients:
+ Antony.Lee |
2015-07-16 22:43:05 | Antony.Lee | set | messageid: <1437086585.22.0.878051480873.issue24649@psf.upfronthosting.co.za> |
2015-07-16 22:43:05 | Antony.Lee | link | issue24649 messages |
2015-07-16 22:43:04 | Antony.Lee | create | |
|