[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout

Change by Carlo Dri : -- versions: +Python 3.8 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout

Carlo Dri added the comment: In agree with this proposal! I was looking for the exact same possibility of specifying a timeout to the accept() method, both in AF_INET and AF_PIPE sockets. If there is any better way to implement this I would love to hear it. -- nosy: +carlodri

[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout

Tom Cook added the comment: The same goes for `Connection.recv()`, as in the sample code another case where the thread will never terminate is when a `Client` is connected to the socket but never sends any messages; in this case, the call to `recv()` will block forever.

[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout

New submission from Tom Cook : If nothing connects to it, `multiprocessing.connection.Listener.accept()` will block forever with no good way to interrupt it. Supposing that a thread implements a loop like this: def run(self): l = Listener(socket_path,