[issue42117] asyncio calls from sync/async, better docs or api support

Blaze Spinnaker added the comment: Ah, thanks. Looked around for something like that but couldn't find it. Will close this. -- ___ Python tracker ___

[issue42117] asyncio calls from sync/async, better docs or api support

Change by Blaze Spinnaker : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue42117] asyncio calls from sync/async, better docs or api support

Dima Tisnek added the comment: Blaze, I think this needs a concrete proposal: either a patch, or at least a formal example how the new API would be used. Note that there's also async-sig mailing list that's less formal, as well as discuss.python.org to bounce ideas off others. --

[issue42117] asyncio calls from sync/async, better docs or api support

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.

[issue42117] asyncio calls from sync/async, better docs or api support

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. --

[issue42117] asyncio calls from sync/async, better docs or api support

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

[issue42117] asyncio calls from sync/async, better docs or api support

Yury Selivanov added the comment: I'm not sure what you're actually proposing, and only have a vague understanding of what you're complaining about. This is perhaps related to https://bugs.python.org/issue33523? If so then maybe leave a comment there? --

[issue42117] asyncio calls from sync/async, better docs or api support

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

[issue42117] asyncio calls from sync/async, better docs or api support

Change by Blaze Spinnaker : -- versions: +Python 3.10, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ ___

[issue42117] asyncio calls from sync/async, better docs or api support

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