homepage

We face yesterday a bug in a project, and after a few hours of investigation we found a bad/not documented behavior in multiprocessing.Queue.
If you put one or more items in a queue and if the items are large, there is a delay between the put is executed and the item is finally available in the queue. This is reasonable because the underlying thread and the pipe, but the problem is not this.
The problem is that Queue.qsize() is reporting the number of items put, Queue.empty() is returning True, and Queue.get() is raising Empty.
So, the only safe method to get all the items is as follows:
while q.qsize(): 
 try: 
 item = q.get_nowait() 
 except Empty: 
 pass
Which is not very nice.
I attach a sample file reproducing the behavior, a single process put 100 elements in a Queue and after that it tries to get all of them, I tested in python 2.7.9 and 3.4 with the same result (seems python3 is a little bit faster and you need to enlarge the items). Also if you wait between get's, the process is able to retrieve all the items.

This is the documented behavior. "qsize: Return the approximate size of the queue. Note, qsize() > 0 doesn't guarantee that a subsequent get() will not block, nor will qsize() < maxsize guarantee that put() will not block."
It looks like what you want here is get with a timeout, not get_nowait.

I think you misunderstood my explanation. My english is not very good, sorry.
I think that my previously attached file (mpqueuegetwrong.py) shows it better than my words. In this file you can see that I am not calling qsize nor get_nowait, only put and get. And the behavior I am reporting is only related to those methods (and I think it is not documented).

You are calling q.empty when draining the queue. That has the same documented caution. Since you are using get in that loop, in that case you *want* to be calling qsize, just like you do when you drain it at the end.

That's not my point.
To my understanding, when you put a item in the queue the item *must* be available to get in the next call. So I think put should block until the item is really in the queue so when you call get it return *always* and not some times (depending on the item size).
If this is not the expected behavior I think it should be warned in the put/get method.