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 sbt
Recipients Garrett.Moore, docs@python, sbt
Date 2012-03-06.12:28:36
SpamBayes Score 4.5855772e-06
Marked as misclassified No
Message-id <1331036917.64.0.574146881806.issue14206@psf.upfronthosting.co.za>
In-reply-to
Content
What you were told on IRC was wrong.  By default the queue *does* have infinite size.

When a process puts an item on the queue for the first time, a background thread is started which is responsible for writing items to the underlying pipe.  This does mean that, on exit, the process should wait for the background thread to flush all the data to the pipe.  This happens automatically unless you specifically prevent it by calling cancel_join_thread() method.

If you stick to those methods supported by standard queue objects, then things should work correctly.  

(Maybe cancel_join_thread() would be better named allow_exit_without_flush().)
History
Date User Action Args
2012-03-06 12:28:37sbtsetrecipients: + sbt, docs@python, Garrett.Moore
2012-03-06 12:28:37sbtsetmessageid: <1331036917.64.0.574146881806.issue14206@psf.upfronthosting.co.za>
2012-03-06 12:28:37sbtlinkissue14206 messages
2012-03-06 12:28:36sbtcreate