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 josh.r
Recipients jnoller, josh.r, sbt
Date 2016-05-02.20:45:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1462221906.35.0.299734834311.issue26905@psf.upfronthosting.co.za>
In-reply-to
Content
The Queue module (queue on Py3) is for communication between threads, not processes; what you've written wouldn't behave correctly on any version of Python. You want to use multiprocessing's Queue class, not Queue.Queue, and to avoid possible deadlocks, you want to populate it after the pool workers are running.

In any event, id(q) is expected to match on Linux, which has fork semantics (so the memory space in parent and child is initially identical). On Windows it differs because spawn based multiprocessing means the objects are recreated in the child processes, rather than inherited directly.

This is a problem with your code and understanding on forking, not a problem in Python.
History
Date User Action Args
2016-05-02 20:45:06josh.rsetrecipients: + josh.r, jnoller, sbt
2016-05-02 20:45:06josh.rsetmessageid: <1462221906.35.0.299734834311.issue26905@psf.upfronthosting.co.za>
2016-05-02 20:45:06josh.rlinkissue26905 messages
2016-05-02 20:45:05josh.rcreate