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 takluyver
Recipients davin, kormang, myles.steinhauser, pitrou, shnizzedy, takluyver
Date 2021-12-06.10:37:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1638787031.6.0.511494580487.issue43805@roundup.psfhosted.org>
In-reply-to
Content
It's not my decision, so I can't really say. But the Queue API is pretty stable, and exists 3 times over in Python (the queue module for use with threads, in multiprocessing and in asyncio). So I'd guess that anyone wanting to add to that API would need to make a compelling case for why it's important, and be prepared for a lot of wrangling over API details (like method names and exceptions).

If you want to push that idea, you could try the ideas board on the Python discourse forum: https://discuss.python.org/c/ideas/6 .

You might also want to look at previous discussions about adding a Queue.close() method: issue29701 and issue40888.
History
Date User Action Args
2021-12-06 10:37:11takluyversetrecipients: + takluyver, pitrou, davin, kormang, shnizzedy, myles.steinhauser
2021-12-06 10:37:11takluyversetmessageid: <1638787031.6.0.511494580487.issue43805@roundup.psfhosted.org>
2021-12-06 10:37:11takluyverlinkissue43805 messages
2021-12-06 10:37:11takluyvercreate