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 asvetlov
Recipients asvetlov, yselivanov
Date 2019-10-27.23:55:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572220517.17.0.719967711059.issue38599@roundup.psfhosted.org>
In-reply-to
Content
I have a different feeling: we should start raising deprecation for asyncio.Queue() if it is created without running event loop.

It required `get_event_loop()` and `loop.is_running()` checks.

Later the pair can be replaced with `get_running_loop()`.

I think no check at awaiting time is needed; we never do it for other asyncio parts.  Just control of the loop at creation time is enough; if the object is created inside a running loop the sane code will use it with this loop context always.
History
Date User Action Args
2019-10-27 23:55:17asvetlovsetrecipients: + asvetlov, yselivanov
2019-10-27 23:55:17asvetlovsetmessageid: <1572220517.17.0.719967711059.issue38599@roundup.psfhosted.org>
2019-10-27 23:55:17asvetlovlinkissue38599 messages
2019-10-27 23:55:17asvetlovcreate