[issue14206] multiprocessing.Queue documentation is lacking important details

2013-07-02 Thread Richard Oudkerk
Changes by Richard Oudkerk : -- resolution: -> fixed stage: -> committed/rejected ___ Python tracker ___ ___ Python-bugs-list mailin

[issue14206] multiprocessing.Queue documentation is lacking important details

2013-07-02 Thread Richard Oudkerk
Changes by Richard Oudkerk : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue14206] multiprocessing.Queue documentation is lacking important details

2013-07-02 Thread Roundup Robot
Roundup Robot added the comment: New changeset f35401dba89f by Richard Oudkerk in branch '2.7': Issue #14206: Clarify docs for Queue.join_cancel_thread(). http://hg.python.org/cpython/rev/f35401dba89f New changeset 9746f217a270 by Richard Oudkerk in branch '3.3': Issue #14206: Clarify docs for Q

[issue14206] multiprocessing.Queue documentation is lacking important details

2012-03-06 Thread sbt
sbt added the comment: 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 exi

[issue14206] multiprocessing.Queue documentation is lacking important details

2012-03-05 Thread Garrett Moore
New submission from Garrett Moore : 1) If cancel_join_thread() is called, data may be lost. This is not explicitly stated. I had multiple writers put() data in a Queue, and wanted to have the workers finish before I began consuming the data. This caused a deadlock because my Queue was not empt