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 davin
Recipients Bernhard10, davin, docs@python, r.david.murray
Date 2016-12-14.16:33:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
All communication between processes in multiprocessing has consistently used pickle to serialize the data being communicated (this includes what is described in the "Shared memory" section of the docs).  The documentation has not done a great job of making this clear, instead only describing the requirement that data be pickleable in select places.  For example, in the section on Queues:
    Note: When an object is put on a queue, the object is pickled and a
    background thread later flushes the pickled data to an underlying pipe.

Though it only applies to 3.6+, issue28053 still needs its own documentation improvement to make clear that the mechanism for communicating data defaults to serialization by pickle but that this can be replaced by alternatives.

I agree that the documentation around the use of pickle in multiprocessing deserves improvement.
Date User Action Args
2016-12-14 16:33:49davinsetrecipients: + davin, r.david.murray, docs@python, Bernhard10
2016-12-14 16:33:49davinsetmessageid: <>
2016-12-14 16:33:49davinlinkissue28973 messages
2016-12-14 16:33:49davincreate