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 Martin.Teichmann
Recipients Martin.Teichmann, asvetlov, cjrh, yselivanov
Date 2019-11-22.17:31:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, in the one-producer-many-consumers situation on can indeed to the trick with the None. But this is just a clumsy hack, cancelling the tasks is IMHO more in line with asyncio.

In the many-producers-one-consumer scenario this does not work. The one dead consumer cannot feed back to the producers. Sure, there are still many hacks imaginable, but a closing or cancelling the queue is a very clear way of doing things.

As for the naming: I personally don't care, close() or cancel() are both fine with me.
Date User Action Args
2019-11-22 17:31:14Martin.Teichmannsetrecipients: + Martin.Teichmann, asvetlov, cjrh, yselivanov
2019-11-22 17:31:14Martin.Teichmannsetmessageid: <>
2019-11-22 17:31:14Martin.Teichmannlinkissue37334 messages
2019-11-22 17:31:13Martin.Teichmanncreate