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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, gvanrossum, ronaldoussoren
Date 2007-11-27.08:20:26
SpamBayes Score 0.0011198674
Marked as misclassified No
Message-id <1196151627.19.0.803306755318.issue1402@psf.upfronthosting.co.za>
In-reply-to
Content
> The _PyGILState_Fini function might cause user code to run as well, 
> it removes the thread-local variable that contains the PyThreadState 
> for threads, and that contains some Python objects that might contain 
> arbitrary values (such as the last exception value). 

No, _PyGILState_Fini does not invoke any python code; it only clears C
variables. The last exception value is deleted during the call to 
PyInterpreterState_Clear() (inside PyThreadState_Clear).
History
Date User Action Args
2007-11-27 08:20:27amaury.forgeotdarcsetspambayes_score: 0.00111987 -> 0.0011198674
recipients: + amaury.forgeotdarc, gvanrossum, ronaldoussoren
2007-11-27 08:20:27amaury.forgeotdarcsetspambayes_score: 0.00111987 -> 0.00111987
messageid: <1196151627.19.0.803306755318.issue1402@psf.upfronthosting.co.za>
2007-11-27 08:20:27amaury.forgeotdarclinkissue1402 messages
2007-11-27 08:20:26amaury.forgeotdarccreate