On Mon, Jan 8, 2018 at 7:27 PM, Amit Green <amit.mi...@gmail.com> wrote:
> An argument against this API, is that any caller of recv should be doing > error handling (i.e.: catching exceptions from the socket). > It's still not entirely clear, but I'm pretty sure this thread is talking about multiprocessing.Connection objects, which don't have anything to do with sockets. (I think. They might use sockets internally on some platforms.) The only documented error from multiprocessing.Connection.recv is EOFError, which is basically equivalent to a StopIteration. I'm surprised that multiprocessing.Connection isn't iterable -- it seems like an obvious oversight. -n -- Nathaniel J. Smith -- https://vorpus.org <http://vorpus.org>
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
