[issue2699] Exception name improperly indented

Brett Cannon <[EMAIL PROTECTED]> added the comment: Fix in revision 62555. -- resolution: -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2699] Exception name improperly indented

Brett Cannon <[EMAIL PROTECTED]> added the comment: On Sun, Apr 27, 2008 at 2:34 AM, Georg Brandl <[EMAIL PROTECTED]> wrote: > > Georg Brandl <[EMAIL PROTECTED]> added the comment: > > You could add a function to the _testcapi module to invoke PyErr_Display. > That's true and probably the only

[issue2699] Exception name improperly indented

Georg Brandl <[EMAIL PROTECTED]> added the comment: You could add a function to the _testcapi module to invoke PyErr_Display. -- nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]> __ _

[issue2699] Exception name improperly indented

Brett Cannon <[EMAIL PROTECTED]> added the comment: Yep. I already did that and ran the unit test suite to verify. Now I am just trying to figure out how to best test it. It seems it only comes up for printing a traceback. That would mean either using subprocess to run another interpreter and

[issue2699] Exception name improperly indented

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: It looks like you can just remove the offending line like so: Index: Python/traceback.c === --- Python/traceback.c (revision 62515) +++ Python/traceback.c (working copy) @@

[issue2699] Exception name improperly indented

Brett Cannon <[EMAIL PROTECTED]> added the comment: Forgot to mention this is probably from Python/traceback.c:tb_displayline(). __ Tracker <[EMAIL PROTECTED]> __ __

[issue2699] Exception name improperly indented

New submission from Brett Cannon <[EMAIL PROTECTED]>: The new warnings implementation tweaks how tracebacks are printed. This introduced a bug where the exception name is indented when it shouldn't be: e.g., ``raise KeyError`` should look like:: Traceback (most recent call last): File ""