Message 233789 - Python tracker

➜

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	ncoghlan, pitrou, serhiy.storchaka
Date	2015-01-10.00:07:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1420848454.08.0.909579778924.issue23188@psf.upfronthosting.co.za>
In-reply-to

Content
> The interesting discovery I made while reviewing the patch for issue > 22906 is that there apparently is implicit chaining support in > PyErr_SetObject Indeed, there is, and it should work properly (AFAIR there was quite a bit of debugging to make this work). Also, note that normalizing is already handled. I'm not sure what you're witnessing that doesn't work as expected. I suspect that you may be confusing "an exception has been caught" (and is ready to be chained from) with "an exception has been raised" (i.e. PyErr_Occurred() is true).

> The interesting discovery I made while reviewing the patch for issue 
> 22906 is that there apparently *is* implicit chaining support in
> PyErr_SetObject

Indeed, there is, and it should work properly (AFAIR there was quite a bit of debugging to make this work). Also, note that normalizing is already handled.

I'm not sure what you're witnessing that doesn't work as expected. I suspect that you may be confusing "an exception has been caught" (and is ready to be chained from) with "an exception has been raised" (i.e. PyErr_Occurred() is true).

History
Date	User	Action	Args
2015-01-10 00:07:34	pitrou	set	recipients: + pitrou, ncoghlan, serhiy.storchaka
2015-01-10 00:07:34	pitrou	set	messageid: <1420848454.08.0.909579778924.issue23188@psf.upfronthosting.co.za>
2015-01-10 00:07:34	pitrou	link	issue23188 messages
2015-01-10 00:07:33	pitrou	create