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 vstinner
Recipients amaury.forgeotdarc, benjamin.peterson, pitrou, vstinner
Date 2008-08-21.23:26:19
SpamBayes Score 0.0013188896
Marked as misclassified No
Message-id <1219361181.01.0.516081202164.issue3611@psf.upfronthosting.co.za>
In-reply-to
Content
It's now known that PyErr_SetObject() have to be re-entrant because of 
the garbage collector interaction. As I wrote in my comments, tstate 
may be changed during PyEval_CallObject() call. The problem is to 
known which values have to be protected during PyErr_SetObject() 
re-entrant call... I tried to save/restore tstate->exc_value if it's 
value changes, but I'm not sure that it's enough.
History
Date User Action Args
2008-08-21 23:26:21vstinnersetrecipients: + vstinner, amaury.forgeotdarc, pitrou, benjamin.peterson
2008-08-21 23:26:21vstinnersetmessageid: <1219361181.01.0.516081202164.issue3611@psf.upfronthosting.co.za>
2008-08-21 23:26:20vstinnerlinkissue3611 messages
2008-08-21 23:26:20vstinnercreate