[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

New submission from R. David Murray : In python3 if an error is raised from ErrorRaisingArgumentParser that is not caught by an assertRaises, unittest prints out the traceback, which is a chained traceback including the SystemExit that the argparse test suite catches in order to produce the Ar

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

R. David Murray added the comment: I can't find anyway to actually do what I suggested. There doesn't seem to be any way to break the traceback chain. -- ___ Python tracker ___

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

R. David Murray added the comment: See issue 6210. The attached patch uses the workaround from that issue. -- keywords: +patch Added file: http://bugs.python.org/file18351/argparse_test_raise.patch ___ Python tracker

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Mark Lawrence added the comment: Presumably the implementation of PEP 409 on issue 6210 can be used to fix this problem. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Changes by Adam Collard : -- nosy: +adam-collard ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Adam Collard added the comment: Use raise from None to avoid additional exception context -- Added file: http://bugs.python.org/file30800/argparse-raise-from-None ___ Python tracker _

[issue9495] argparse unittest tracebacks are confusing if an error is raised when not expected

Changes by Ezio Melotti : -- keywords: -easy nosy: +ezio.melotti stage: needs patch -> patch review versions: +Python 3.3, Python 3.4 -Python 3.1, Python 3.2 ___ Python tracker _