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 yselivanov
Recipients asvetlov, lschoe, yselivanov
Date 2019-10-28.22:23:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
> Well, I'm basically using a run method defined as a shorthand for self.loop.run_until_complete (without closing loop, reusing it throughout). It would be nice if asyncio.run could simply be used instead, but I understand you're saying this is easier said than done, which is fine with me. Thanks.

Yes. `asyncio.run()` is similar to `loop.run_until_complete()` but adds some guarantees + sane setup/cleanup. If we strip proper cleanup then there's no point in `asyncio.run()`.  So using `loop.run_until_complete()` is totally fine when you want to preserve the event loop between runs.
History
Date User Action Args
2019-10-28 22:23:41yselivanovsetrecipients: + yselivanov, asvetlov, lschoe
2019-10-28 22:23:41yselivanovsetmessageid: <[email protected]>
2019-10-28 22:23:41yselivanovlinkissue38599 messages
2019-10-28 22:23:41yselivanovcreate