This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients r.david.murray
Date 2010-08-03.16:21:53
SpamBayes Score 0.00252505
Marked as misclassified No
Message-id <1280852518.56.0.709280463518.issue9495@psf.upfronthosting.co.za>
In-reply-to
Content
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 ArgumentParserError that is actually of interest.  I think the argparse test suite should break that chain to make the tracebacks when failures happen more on-point.
History
Date User Action Args
2010-08-03 16:21:58r.david.murraysetrecipients: + r.david.murray
2010-08-03 16:21:58r.david.murraysetmessageid: <1280852518.56.0.709280463518.issue9495@psf.upfronthosting.co.za>
2010-08-03 16:21:53r.david.murraylinkissue9495 messages
2010-08-03 16:21:53r.david.murraycreate