[issue24649] python -mtrace --help is wrong

SilentGhost added the comment: A re-write using argparse is submitted in the issue22642, that's why I'm closing this issue. Changes from Evan's patch were incorporated in the submitted patch there. -- nosy: +SilentGhost resolution: -> out of date stage: needs patch -> resolved status:

[issue24649] python -mtrace --help is wrong

Evan Hubinger added the comment: Added a patch that clears up the incorrect help. It now accurately reflects the only constraints that the code actually puts on the arguments: if listfuncs and (count or trace): _err_exit("cannot specify both --listfuncs and (--trace or --count)")

[issue24649] python -mtrace --help is wrong

Alexander Belopolsky added the comment: Maybe it is time to rewrite trace module argument parser using argparse and get an "always correct" auto-generated help for free? -- keywords: +easy stage: -> needs patch versions: +Python 3.6 -Python 3.5 ___ P

[issue24649] python -mtrace --help is wrong

Changes by Terry J. Reedy : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue24649] python -mtrace --help is wrong

New submission from Antony Lee: 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] [ARGS] Meta-options: --helpDisplay this help then exit. --version Output version