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 jpe
Recipients jnoller, jpe, ocean-city
Date 2009-04-01.19:45:15
SpamBayes Score 2.19114e-10
Marked as misclassified No
Message-id <49D3C43F.1060506@wingware.com>
In-reply-to <1238603856.94.0.671908579552.issue3551@psf.upfronthosting.co.za>
Content
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.
History
Date User Action Args
2009-04-01 19:45:18jpesetrecipients: + jpe, ocean-city, jnoller
2009-04-01 19:45:16jpelinkissue3551 messages
2009-04-01 19:45:15jpecreate