[issue28973] The fact that multiprocess.Queue uses serialization should be documented.

Davin Potts added the comment: 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 c

[issue28973] The fact that multiprocess.Queue uses serialization should be documented.

R. David Murray added the comment: Yeah, that's why I said "in the general case". Making it clear in the overview seems reasonable to me. -- ___ Python tracker ___

[issue28973] The fact that multiprocess.Queue uses serialization should be documented.

Bernhard10 added the comment: My first thought was that Queue was implemented using shared memory. I guess from the fact that the "Shared memory" section is separate in the multiprocessing documentation I should have known better, though. So I guess some clarification in the documentation would

[issue28973] The fact that multiprocess.Queue uses serialization should be documented.

R. David Murray added the comment: That fact that this is so is implicit in the name multi*process*ing and the documented restrictions of the id function. That is, it is the purpose of the module is to manage computation across multiple processes. Since different processes have distinct memor

[issue28973] The fact that multiprocess.Queue uses serialization should be documented.

Bernhard10 added the comment: See http://stackoverflow.com/a/925241/5069869 Apparently multiprocessing.Queue uses pickle to serialize the objects in the queue, which explains the change of identity, but is absolutely unclear from the documentation. -- assignee: -> docs@python compone