[issue5573] multiprocessing Pipe poll() and recv() semantics.

[Vaibhav Mallya]

Vaibhav Mallya <mallyvai at umich.edu> added the comment:

On second thought, it seems like it shouldn't make sense. This forces a
destructive check. Suppose we do child.poll() and then child.recv() but
it's legitimate data; that data will be removed from the queue even if
we just wanted to check if the pipe was alive. This seems like it
shouldn't have to happen.

I'm unfamiliar with the lower level workings of sockets; is this
destructive checking behavior forced by the socket internals? Is it
standard?

----------

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