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 pitrou
Recipients flox, ggenellina, guettli, hoffman, ncoghlan, news1234, pakal, pitrou, r.david.murray, stutzbach, vinay.sajip, vstinner, ysj.ray
Date 2012-10-30.19:50:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1351626642.93.0.529952488612.issue1553375@psf.upfronthosting.co.za>
In-reply-to
Content
I recently re-wrote something like this, so I think this is useful.
I wonder if it wouldn't be nice to add a caret or some similar marker indicating the frame where the exception was caught, e.g.:


Traceback (most recent call last, catch point highlighted):
  File "testmod.py", line 13, in <module>
    upper()
> File "testmod.py", line 11, in upper
    foo()
  File "testmod.py", line 6, in foo
    raise Exception
Exception
History
Date User Action Args
2012-10-30 19:50:43pitrousetrecipients: + pitrou, vinay.sajip, guettli, hoffman, ncoghlan, ggenellina, vstinner, stutzbach, pakal, r.david.murray, flox, news1234, ysj.ray
2012-10-30 19:50:42pitrousetmessageid: <1351626642.93.0.529952488612.issue1553375@psf.upfronthosting.co.za>
2012-10-30 19:50:42pitroulinkissue1553375 messages
2012-10-30 19:50:42pitroucreate