Message304283
And the actual exit is via `parse.error` and `parse.exit`, which are documented in 16.4.5.9.
When run interactively in Ipython, exits (including the help) are captured and displayed with:
In [896]: parser.parse_args()
usage: ipython3 [-h] [--one | --two | --six]
ipython3: error: unrecognized arguments: --pylab --nosep --term-title --InteractiveShellApp.pylab_import_all=False
An exception has occurred, use %tb to see the full traceback.
SystemExit: 2
The exit makes unittesting a challenge. 'test_argparse.py' resolves this by using a subclassed parser, one that changes the error/exit, and also redirects output. |
|
Date |
User |
Action |
Args |
2017-10-12 19:19:21 | paul.j3 | set | recipients:
+ paul.j3, CharlesMerriam, r.david.murray, docs@python |
2017-10-12 19:19:21 | paul.j3 | set | messageid: <1507835961.61.0.213398074469.issue31640@psf.upfronthosting.co.za> |
2017-10-12 19:19:21 | paul.j3 | link | issue31640 messages |
2017-10-12 19:19:21 | paul.j3 | create | |
|