[issue7318] multiprocessing should not wait endlessly

Kristján Valur Jónsson added the comment: See also issue 7314 -- nosy: +krisvale ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue7318] multiprocessing should not wait endlessly

Jesse Noller added the comment: On Nov 13, 2009, at 5:40 PM, Antoine Pitrou wrote: > > Antoine Pitrou added the comment: > > Ok, this is now committed to all 4 branches. Amusingly, it seems to > solve the test_multiprocessing freeze/failure problem in py3k... > (I still hope you can find so

[issue7318] multiprocessing should not wait endlessly

Antoine Pitrou added the comment: Ok, this is now committed to all 4 branches. Amusingly, it seems to solve the test_multiprocessing freeze/failure problem in py3k... (I still hope you can find some time to make multiprocessing more robust and less baroque inside!) -- resolution: -> fi

[issue7318] multiprocessing should not wait endlessly

Jesse Noller added the comment: Passes on OS/X 10.6.2, I'm ok with it -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue7318] multiprocessing should not wait endlessly

Jesse Noller added the comment: Patch seems fine, going to test it against trunk locally -- ___ Python tracker ___ ___ Python-bugs-lis

[issue7318] multiprocessing should not wait endlessly

Antoine Pitrou added the comment: Please review. -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file15323/mptimeout.patch ___ Python tracker __

[issue7318] multiprocessing should not wait endlessly

New submission from Antoine Pitrou : SocketClient() in multiprocessing.connection loops endlessly when the connection is refused. It shouldn't, and instead use a timeout. This is especially annoying since SocketClient() can be called as part of finalizing an object, which makes debugging very ann