New submission from R. David Murray <rdmur...@bitdance.com>: 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.
---------- components: Tests keywords: easy messages: 112625 nosy: r.david.murray priority: low severity: normal stage: needs patch status: open title: argparse unittest tracebacks are confusing if an error is raised when not expected type: behavior versions: Python 3.1, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue9495> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
