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 davin, jnoller, ppperry, sbt
Date 2016-07-02.20:17:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467490673.68.0.146419230894.issue27081@psf.upfronthosting.co.za>
In-reply-to
Content
I took the example snippet and cleaned things up a bit, adding some crude timestamping and commentary.  (Attached)

In the example, when the Process finally dies, a lot of information has been put onto the Queue but it hasn't necessarily had enough time to be synced to the parent process so it may be only a truncated subset of the data that remains available/visible/retrievable on the parent.  How much data gets synced to the parent depends on many factors and should even vary from one run to another.

That is to say that a multiprocessing.Queue is not going to hold up a dying process to finish communicating data to other processes.
History
Date User Action Args
2016-07-02 20:17:53davinsetrecipients: + davin, jnoller, sbt, ppperry
2016-07-02 20:17:53davinsetmessageid: <1467490673.68.0.146419230894.issue27081@psf.upfronthosting.co.za>
2016-07-02 20:17:53davinlinkissue27081 messages
2016-07-02 20:17:53davincreate