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 pitrou
Recipients asksol, brian.curtin, jnoller, kristjan.jonsson, pitrou, tim.golden
Date 2011-05-07.00:39:43
SpamBayes Score 0.00012344749
Marked as misclassified No
Message-id <>
This doesn't seem to be so easy. WFMO (or WFSO) often seems to return successfully while there's no message to read on the pipe end. Here is a sample session (disturbing results):

>>> a, b = connection.Pipe(True)
>>> win32.WaitForMultipleObjects([a._handle], True, 1000)
>>> win32.WaitForMultipleObjects([b._handle], True, 1000)
>>> win32.PeekNamedPipe(a._handle)
(0, 0)
>>> win32.WaitForMultipleObjects([a._handle], True, 1000)

(do note how the end created with CreateFile() is considered ready by WaitForMultipleObjects, while the end created with CreateNamedPipe() is considered ready after an unsuccessful call to PeekNamedPipe()!)
Date User Action Args
2011-05-07 00:39:44pitrousetrecipients: + pitrou, kristjan.jonsson, tim.golden, jnoller, brian.curtin, asksol
2011-05-07 00:39:44pitrousetmessageid: <>
2011-05-07 00:39:43pitroulinkissue11668 messages
2011-05-07 00:39:43pitroucreate