homepage

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 kristjan.jonsson
Recipients amaury.forgeotdarc, kristjan.jonsson, loewis, mhammond
Date 2009年02月01日.09:51:21
SpamBayes Score 0.0014491568
Marked as misclassified No
Message-id <1233481943.83.0.187632101441.issue4804@psf.upfronthosting.co.za>
In-reply-to
Content
Ah, but I think you missed the main point of the new patch.
There is a counter incremented and decremented. So, the State is set 
only when the first thread enters a guarded section, and then restored 
when the final thread leaves the section. There is no per-thread 
storage of the previous state anymore, only static variables storing 
the "unmodified state" to restore to when the last thread leaves a 
guarded section. As long as some thread is in a guarded section, 
assertions and stuff is turned off, otherwise, we keep the old ones.
This is similar in some ways to the special version of 
Py_BEGIN_ALLOW_THREADS (FILE_BEGIN_ALLOW_THREADS, was it?) used in 
fileio.c.
History
Date User Action Args
2009年02月01日 09:52:24kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, mhammond, amaury.forgeotdarc
2009年02月01日 09:52:23kristjan.jonssonsetmessageid: <1233481943.83.0.187632101441.issue4804@psf.upfronthosting.co.za>
2009年02月01日 09:51:23kristjan.jonssonlinkissue4804 messages
2009年02月01日 09:51:21kristjan.jonssoncreate

AltStyle によって変換されたページ (->オリジナル) /