Boolean representation of Q/queue objects does not fit behaviour of lists etc.

[Frunit]

BPO	24866
Nosy	@rhettinger, @bitdancer

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/rhettinger'
closed_at = <Date 2015-08-15.04:06:58.958>
created_at = <Date 2015-08-14.10:06:01.523>
labels = ['type-bug']
title = 'Boolean representation of Q/queue objects does not fit behaviour of lists etc.'
updated_at = <Date 2015-08-15.04:06:58.956>
user = 'https://bugs.python.org/Frunit'

bugs.python.org fields:

activity = <Date 2015-08-15.04:06:58.956>
actor = 'rhettinger'
assignee = 'rhettinger'
closed = True
closed_date = <Date 2015-08-15.04:06:58.958>
closer = 'rhettinger'
components = []
creation = <Date 2015-08-14.10:06:01.523>
creator = 'Frunit'
dependencies = []
files = []
hgrepos = []
issue_num = 24866
keywords = []
message_count = 3.0
messages = ['248577', '248585', '248634']
nosy_count = 3.0
nosy_names = ['rhettinger', 'r.david.murray', 'Frunit']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue24866'
versions = ['Python 2.7', 'Python 3.4']

[Frunit]

Usually, list-like objects return False when they are empty and True when at least one element is in the list. However, Queue (Python 2) resp. queue (Python 3) objects always return True. I am aware of that objects should always return True unless otherwise stated, but as queues are (at least in my perception) related to lists, they should behave similarly in this case.

Python3 (similar in Python2):
>>> import queue
>>> q = queue.Queue()
>>> bool(q)
True
(Should be False, in my opinion; the same for PriorityQueue and LifoQueue)

I searched for reasons for returning True in empty Queues, but I could not find any in the net or in the Python docs.

[bitdancer]

I believe this is intentional; see the documentation of the "empty' method for the motivation. The reason for not just reflecting the result of an empty call in __bool__ is that not doing so forces you to use empty, which gives you an opportunity to learn about the lack of guarantees. And every time you use it, or read it in someone else's code, you are reminded that a Queue is *different* from a list in this very important way.

[rhettinger]

RDM is correct. Queues having qsize() instead of __len__() was an intentional part of the design. Code relying on the boolean value would be fragile.

FWIW, this code is very old (originally designed by Guido when dinosaurs roamed the earth) and it is far too late to alter its API.