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 brian.curtin, kristjan.jonsson, loewis, pitrou, python-dev, sbt, tim.golden
Date 2012-04-23.21:05:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The vista specific path is included there for completeness, if and when code moves to that platform, besides showing what the "emulated CV" is actually emulating.

Also, I am aware of the old/new GIL, but our console game uses python 2.7 and the old GIL will be living on for many a good year, just like 2.7 will.

But you make a good point.  I had forgotten that the new GIL is actually implemented with emulated condition variables (current version contributed by myself :). I think a different patch is in order, where ceval_gil.h makes use of the platform specific "condition variable" services as declared in thread_platform.h.  There is no point in duplicating code.
Date User Action Args
2012-04-23 21:05:42kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, pitrou, tim.golden, brian.curtin, python-dev, sbt
2012-04-23 21:05:42kristjan.jonssonsetmessageid: <>
2012-04-23 21:05:41kristjan.jonssonlinkissue11618 messages
2012-04-23 21:05:41kristjan.jonssoncreate