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 beazley, dabeaz, kristjan.jonsson, loewis, pitrou
Date 2010-04-03.12:37:33
SpamBayes Score 0.00032382648
Marked as misclassified No
Message-id <1270298255.15.0.238983675567.issue8299@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine:  Please take a look, the change is really simple, particularly the ROUNDROBIN_GIL variant which fixes the originally observed problem.
the GIL is still a lock, implemented using a mutex and a semaphore.  It is modified to work exactly as the lock always has done on windows (which is why the original problem isn't present on that platform).

The simplicity of the change stems from the fact that the gil is still just a mutex-type object, which is aqcuired and released just as it has always been.  The change is in the internal rules of the mutex, making sure that threads queue up properly and (optionally) that they are released in a priority based order.
History
Date User Action Args
2010-04-03 12:37:35kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, beazley, pitrou, dabeaz
2010-04-03 12:37:35kristjan.jonssonsetmessageid: <1270298255.15.0.238983675567.issue8299@psf.upfronthosting.co.za>
2010-04-03 12:37:34kristjan.jonssonlinkissue8299 messages
2010-04-03 12:37:33kristjan.jonssoncreate