Message 185261 - 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	Zdeněk.Pavlas
Recipients	Zdeněk.Pavlas, amaury.forgeotdarc, docs@python, ezio.melotti, mrabarnett
Date	2013-03-26.08:22:29
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1364286149.58.0.0861407304606.issue17544@psf.upfronthosting.co.za>
In-reply-to

Content
Yes, found that certain IO operations re-raise the error, too. However, if the Python runtime expects extension writers to keep tstate->curexc_type clear, it should be documented in http://docs.python.org/2/c-api/exceptions.html There's not a single use case of PyErr_Clear() mentioned.

Yes, found that *certain* IO operations re-raise the error, too.  However, if the Python runtime expects extension writers to keep tstate->curexc_type clear, it should be documented in

http://docs.python.org/2/c-api/exceptions.html

There's not a single use case of PyErr_Clear() mentioned.

History
Date	User	Action	Args
2013-03-26 08:22:29	Zdeněk.Pavlas	set	recipients: + Zdeněk.Pavlas, amaury.forgeotdarc, ezio.melotti, mrabarnett, docs@python
2013-03-26 08:22:29	Zdeněk.Pavlas	set	messageid: <1364286149.58.0.0861407304606.issue17544@psf.upfronthosting.co.za>
2013-03-26 08:22:29	Zdeněk.Pavlas	link	issue17544 messages
2013-03-26 08:22:29	Zdeněk.Pavlas	create