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 vstinner
Recipients neologix, vstinner
Date 2011-09-18.09:56:52
SpamBayes Score 3.7368295e-07
Marked as misclassified No
Message-id <1316339813.1.0.605581029272.issue12996@psf.upfronthosting.co.za>
In-reply-to
Content
"Since the rewrite in pure Python of multiprocessing.Connection (issue #11743), multiprocessing.Connection sends and receives the length of the data (used as header) in host byte order."

I don't think so, the C code uses also the host endian. This issue is a feature request.

I don't know if anyone uses multiprocessing on different hosts (because it doesn't work currently).

If you would like to support using multiprocessing on different hosts, it should be documented in multiprocessing doc.
History
Date User Action Args
2011-09-18 09:56:53vstinnersetrecipients: + vstinner, neologix
2011-09-18 09:56:53vstinnersetmessageid: <1316339813.1.0.605581029272.issue12996@psf.upfronthosting.co.za>
2011-09-18 09:56:52vstinnerlinkissue12996 messages
2011-09-18 09:56:52vstinnercreate