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 kristjan.jonsson
Date 2008-11-10.11:36:32
SpamBayes Score 0.00033707725
Marked as misclassified No
Message-id <1226316995.54.0.445551761995.issue4293@psf.upfronthosting.co.za>
In-reply-to
Content
At CCP We have started using the Py_AddPendingCall() mechanism to 
signal python about a completed IO operation.
However, we noticed that the existing mechanism was hoplelessly un-
thread safe.  This is bad, since on Windows at least, it is very 
convenient to have such callbacks happen on an arbitrary thread from 
the system's thread pool.
I submit a thread-safe implementation instead to be used if WITH_THREAD 
is defined.
This allows Py_AddPendingCall() to be called from any thread, from any 
context, even from a PendingCall callback itself.
History
Date User Action Args
2008-11-10 11:36:35kristjan.jonssonsetrecipients: + kristjan.jonsson
2008-11-10 11:36:35kristjan.jonssonsetmessageid: <1226316995.54.0.445551761995.issue4293@psf.upfronthosting.co.za>
2008-11-10 11:36:34kristjan.jonssonlinkissue4293 messages
2008-11-10 11:36:34kristjan.jonssoncreate