Jesse Noller <jnol...@gmail.com> added the comment: On Wed, Apr 1, 2009 at 2:45 PM, John Ehresman <rep...@bugs.python.org> wrote: > > John Ehresman <j...@wingware.com> added the comment: > > Looking into this a bit more and reading the documentation (sorry, I > picked this up because I know something about win32 and not because I > know multiprocessing), it looks like a connection is supposed to be > message oriented and not byte oriented so that a recv() should return > what is sent in a single send(). This is like how Queue works in the > threading case. Note that I think the method signature when using the > dummy.connection differ when using pipe_connection and that the two > differ in what happens when several send_bytes's occur before a recv_bytes > > I'm currently leaning toward essentially leaving the current behavior > (and documenting it) though maybe with a better exception and > documenting that large byte arrays can't be sent through the pipe. > What's still an issue is if a pickle ends up being too large. >
I think I'm fine with this as well, let's documents/add an exception - as for the pickle being too large, I think for now we're safe documenting it ---------- title: multiprocessing.Pipe terminates with ERROR_NO_SYSTEM_RESOURCES if large data is sent (win2000) -> multiprocessing.Pipe terminates with ERROR_NO_SYSTEM_RESOURCES if large data is sent (win2000) _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3551> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
