> Could you be more specific about these tools? They sound like they
may be what Celelibi is looking for. Just a list of APIs (even just a
few core items) would likely point them at the right parts of the
doc.
Sorry if it wasn't clear, but by "interoperability tools", I was referring
to the API
Kyle Stanley writes:
> Fundamentally, OS threads and coroutines are two entirely different
> models of concurrency; though, we do have interoperability tools in
> place and are actively working on making them easier to
> utilize. Also, with adequate arguments for specific real-world use
>
I would like to clarify that asyncio *does* most certainly provide support
for programs that use multiple event loops and interact with a number of
different threads. So, asyncio can definitely be used outside of a purely
"single-process, single-threaded, single-event-loop
approach". However, a
Fortunately, Guido has jumped in. He's the authority on asyncio. I
recommend you consider his advice very carefully. Here are a couple
more commments that I had already written when I saw his post.
Celelibi writes:
> But that doesn't mean we can't try to design asyncio to be more
>
Thanks for switching to python-ideas.
On Mon, Jun 8, 2020 at 12:35 AM Celelibi wrote:
> On Sun, Jun 07, 2020 at 03:47:05PM +0900, Stephen J. Turnbull wrote:
> > Hi, Celelibi,
> >
> > Welcome to Python Ideas.
> >
> > Python Dev is more for discussions of implementations of proposed
> > features,
On Sun, Jun 07, 2020 at 03:47:05PM +0900, Stephen J. Turnbull wrote:
> Hi, Celelibi,
>
> Welcome to Python Ideas.
>
> Python Dev is more for discussions of implementations of proposed
> features, typically clearly on their way to an accepted pull request
> into master. Python-Ideas is a better
