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 ncoghlan
Recipients ggenellina, guettli, hoffman, ncoghlan, news1234, pakal, r.david.murray, vinay.sajip, ysj.ray
Date 2010-11-14.12:47:13
SpamBayes Score 2.2230324e-05
Marked as misclassified No
Message-id <>
Note that after the loop over the values is complete, the final value of tb should correctly refer to the traceback for the exception currently being handled regardless of whether or not any chaining is involved.

So moving the stack printing code that is currently inside the loop after the loop should do the right thing.

With my suggested change in the display layout, I think this idea is still worthwhile (getting it right in handling code is tricky, especially if the exception is passed around before being displayed).
Date User Action Args
2010-11-14 12:47:15ncoghlansetrecipients: + ncoghlan, vinay.sajip, guettli, hoffman, ggenellina, pakal, r.david.murray, news1234, ysj.ray
2010-11-14 12:47:15ncoghlansetmessageid: <>
2010-11-14 12:47:13ncoghlanlinkissue1553375 messages
2010-11-14 12:47:13ncoghlancreate