[issue12328] multiprocessing's overlapped PipeConnection on Windows

[sbt]

sbt <shibturn at gmail.com> added the comment:

I have noticed a few more problems.

* Because poll() isn't thread safe on Windows, neither is Queue.empty().  Since a queue's pipe will never contain empty messages, this can be fixed easily by using (a wrapper for) win32.PeekNamedPipe().

* PipeListener/PipeClient have not been updated to use overlapped I/O.

* If more than one process is to read from a pipe connection then (even with proper synchronisation) we cannot safely use poll() since it can leave a partial message in the pipe.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12328>
_______________________________________