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 jnoller
Recipients eua, jnoller, r.david.murray
Date 2010-03-26.15:20:11
SpamBayes Score 0.00027551377
Marked as misclassified No
Message-id <1269616814.36.0.327823469004.issue8237@psf.upfronthosting.co.za>
In-reply-to
Content
multiprocessing.Queue.Put() acts the same as Queue.put() - if the queue is full, the put call "hangs" until the queue is no longer full. The process will not exit, as the Queue is full, and it's waiting in put.

This works as designed, unless I'm missing something painfully obvious, which is entirely possible.
History
Date User Action Args
2010-03-26 15:20:15jnollersetrecipients: + jnoller, r.david.murray, eua
2010-03-26 15:20:14jnollersetmessageid: <1269616814.36.0.327823469004.issue8237@psf.upfronthosting.co.za>
2010-03-26 15:20:12jnollerlinkissue8237 messages
2010-03-26 15:20:11jnollercreate