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 Rosuav
Recipients Rosuav, belopolsky, gvanrossum, ncoghlan, python-dev, r.david.murray, rhettinger, schlamar, scoder, serhiy.storchaka, vstinner
Date 2015-01-08.10:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420713534.42.0.857206694544.issue22906@psf.upfronthosting.co.za>
In-reply-to
Content
PyErr_Restore doesn't seem to trigger exception chaining. But thanks for the tip about explicitly setting the traceback; not sure how I missed that, but now the StopIteration traceback is visible.

Minor point: The previous patch was setting the __context__ of the RuntimeError, whereas it ought to have been setting __cause__. Have corrected that.

So here, before I move further forward, is a new POC patch; I've removed the patches that rhettinger applied already, and fixed up tracebacks. So now it's a better-behaved POC, at least.
History
Date User Action Args
2015-01-08 10:38:54Rosuavsetrecipients: + Rosuav, gvanrossum, rhettinger, ncoghlan, belopolsky, scoder, vstinner, r.david.murray, python-dev, schlamar, serhiy.storchaka
2015-01-08 10:38:54Rosuavsetmessageid: <1420713534.42.0.857206694544.issue22906@psf.upfronthosting.co.za>
2015-01-08 10:38:54Rosuavlinkissue22906 messages
2015-01-08 10:38:54Rosuavcreate