Author blazespinnaker
Recipients asvetlov, blazespinnaker, yselivanov
Date 2020-10-22.21:44:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603403085.59.0.338672089897.issue42117@roundup.psfhosted.org>
In-reply-to
Content
asyncio code placed in a repl won't execute properly as it may (or may not) be running an event loop already.

This happens not just in traditional repls, but any platform that provides execution shells around code.  Other repls, Spyder, pyppeter, and a lot more.  Some of the maintainers reference running a monkey patch to fix the problem.

The link I provided referenced 40 complaints about this issue.

I am not really proposing anything, just that it be addressed by either new API or better documentation explaining how best to solve the problem.  I do provide an example of an idea.

But addressing is important.  Just leaving it up to the community is causing a lot of chaos, incompatibilities and bugs.   

Some are suggesting using get_event_loop() but you discourage using this api in the documentation.  Not sure what that guidance means exactly as it's not very clear under what constraints the API can be used and when it can't.
History
Date User Action Args
2020-10-22 21:44:45blazespinnakersetrecipients: + blazespinnaker, asvetlov, yselivanov
2020-10-22 21:44:45blazespinnakersetmessageid: <1603403085.59.0.338672089897.issue42117@roundup.psfhosted.org>
2020-10-22 21:44:45blazespinnakerlinkissue42117 messages
2020-10-22 21:44:44blazespinnakercreate