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

Changes by Ask Solem : -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

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

Ask Solem added the comment: I don't know about the socket internals, but I find the behavior acceptable. It may not be feasible to change it now anyway, as there may be people already depending on it (e.g. not handling errors occurring at poll) -- ___

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

Changes by Ask Solem : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/m

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

Changes by Jesse Noller : -- priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

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

Vaibhav Mallya 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.

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

Changes by Jesse Noller : -- assignee: georg.brandl -> jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

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

Changes by Vaibhav Mallya : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

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

New submission from Vaibhav Mallya : Python 2.6.1 (r261:67515, Mar 22 2009, 05:39:39) [GCC 4.2.4 (Ubuntu 4.2.4-1ubuntu4)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from multiprocessing import Pipe >>> parent, child = Pipe() >>> parent.send(1) >>> parent