This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jnoller
Recipients jnoller, jpe, ocean-city
Date 2009-04-01.20:23:03
SpamBayes Score 1.5654145e-13
Marked as misclassified No
Message-id <4222a8490904011323o6656a55ap189e59e36d8a9287@mail.gmail.com>
In-reply-to <49D3C43F.1060506@wingware.com>
Content
On Wed, Apr 1, 2009 at 2:45 PM, John Ehresman <report@bugs.python.org> wrote:
>
> John Ehresman <jpe@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
History
Date User Action Args
2009-04-01 20:23:07jnollersetrecipients: + jnoller, jpe, ocean-city
2009-04-01 20:23:05jnollerlinkissue3551 messages
2009-04-01 20:23:03jnollercreate