[issue35034] Add closing and iteration to threading.Queue

[Vladimir Filipović]

Vladimir Filipović <hemflit at gmail.com> added the comment:

Hi Raymond!

I've posted to python-ideas: https://mail.python.org/pipermail/python-ideas/2018-October/054238.html

The amount of attention it got was modest, so I couldn't exactly say the community has thoroughly vetted and enthusiastically endorsed this proposal :)

But all responses were in the narrow range of neutral to MILDLY positive.
There weren't any objections at all to either the idea or the code. Nor did anybody question whether a feature of this kind should be added at all.

I don't think I could realistically expect much more support than that for a change this minor. (Well, it would have been better if at least one person'd had an (uncontested) strongly positive response.)

Some problems with other kinds of implementations were brought up, but this one isn't vulnerable to them. I believe I've also addressed all your comments from this BPO issue in the opening post there.

An older discussion was linked, which had also shown tacit consensus that this type of feature in general would be welcome.

I suppose it's time to decide if that level of response is enough.

----------
resolution: later -> 
status: closed -> open

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue35034>
_______________________________________