[issue16955] multiprocessing.connection poll() always returns false

2013-01-14 Thread John Brearley
John Brearley added the comment: Hi Rchard: Thanks very much. The wait() method works fine. Regards, John Brearley 613-259-5622 (H) -- ___ Python tracker ___ __

[issue16955] multiprocessing.connection poll() always returns false

2013-01-13 Thread Richard Oudkerk
Richard Oudkerk added the comment: This should be fixed now. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker _

[issue16955] multiprocessing.connection poll() always returns false

2013-01-13 Thread Roundup Robot
Roundup Robot added the comment: New changeset e1c81ab5ad97 by Richard Oudkerk in branch '3.3': Issue #16955: Fix the poll() method for multiprocessing's socket http://hg.python.org/cpython/rev/e1c81ab5ad97 New changeset d904a741afde by Richard Oudkerk in branch 'default': Issue #16955: Fix the

[issue16955] multiprocessing.connection poll() always returns false

2013-01-13 Thread Richard Oudkerk
Richard Oudkerk added the comment: Thanks for the report. It seems to only affect Windows, and only when using sockets rather than pipes. Till this is fixed you could use temp = bool(multiprocessing.connection.wait([cl], 1)) instead of temp = cl.poll(1) As I mentioned on the other

[issue16955] multiprocessing.connection poll() always returns false

2013-01-13 Thread John Brearley
New submission from John Brearley: In the attached multiprocessing.connection simple client script, the poll() method is always returning false. If I force the temp variable to 1, the recv()method happily gets the incoming data. I had hoped to use the poll() method to implement a timeout error