Blaze Spinnaker added the comment:
Ah, thanks. Looked around for something like that but couldn't find it. Will
close this.
--
___
Python tracker
<https://bugs.python.org/issue42
Change by Blaze Spinnaker :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue42117>
___
___
Python-bugs-list
Blaze Spinnaker added the comment:
btw, this is different than the other issue as I understand you don't want
re-entrant calls to async. Library integration can be done (painfully) by
cherry picking the right API to call, but it's more painful with repls as
that's not how they're used
Blaze Spinnaker added the comment:
I guess what I'm saying, is you created a design problem with the sync can't
call async constraint, but didn't suggest any solutions to solving it, and the
solutions people are arriving at are pretty random
Blaze Spinnaker added the comment:
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
Blaze Spinnaker added the comment:
Note that the biggest problem are obviously repls, and there are quite a few
(iPython has issues due to it's high coupling with jupyter). Providing a
contract for them will ensure consistent support across the ecosystem rather
than a hodge podge of barely
Change by Blaze Spinnaker :
--
versions: +Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9
___
Python tracker
<https://bugs.python.org/issue42
New submission from Blaze Spinnaker :
In jupyter / ipython, other repls, as well as from libraries, asyncio code can
be called. To simplify integration, there should be a way for libraries to
transparently do the right thing, call await or start a new global running
event loop.
This can
Blaze Spinnaker added the comment:
I know this issue is closed, but can you folks review:
https://github.com/ipython/ipykernel/issues/548#issuecomment-713637954
The nest_asyncio patch is becoming a defacto contract to fixing this amongst a
lot of people. But the patch doesn't really event
