You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an idea that just popped up randomly when looking through some ray examples / discussion, particularly this trio issue comment: python-trio/trio#2135 (comment)
Can we support an embeddable API for launching the tractor runtime
inside any thread/process spawning system which can run trio?
The short answer is intuitively yes to me, but i'm sure there's quite
a bit that might have to go into it.
Motivations:
bring cross-process SC to any parallel python system (including
GIL-less python or a system that doesn't want to use tractor's
thead/process spawning layer).
allow for interchange-able actor spawning functionality in a
different-framework-based library or platform, as in this ray
example above, or something like numba.nogil if they ever decided
to support compiling async python.
bring parallelism to any python framework that didn't previously have
it outside of GIL releasing extensions or threading usage.
High level API design
we already support open_root_actor() as the entrypoint for starting
the runtime, though maybe we can offer some even lower level hooks for
this.
we would need a way to swap out the spawning layer behind the scenes
(dynamically) for ActorNursery.start_actor().
allow for doing all the ._entry._trio_main() stuff through a public
API in any target child process such that ._runtime._async_main()
gets called / initialized correctly.
this is kinda like the callbacky parts of guest mode:
This is an idea that just popped up randomly when looking through some
ray
examples / discussion, particularly thistrio
issue comment:python-trio/trio#2135 (comment)
Wait wut's the idea?
Can we support an embeddable API for launching the
tractor
runtimeinside any thread/process spawning system which can run
trio
?The short answer is intuitively yes to me, but i'm sure there's quite
a bit that might have to go into it.
Motivations:
GIL-less python or a system that doesn't want to use
tractor
'sthead/process spawning layer).
different-framework-based library or platform, as in this
ray
example above, or something like
numba.nogil
if they ever decidedto support compiling async python.
it outside of GIL releasing extensions or
threading
usage.High level API design
open_root_actor()
as the entrypoint for startingthe runtime, though maybe we can offer some even lower level hooks for
this.
(dynamically) for
ActorNursery.start_actor()
.._entry._trio_main()
stuff through a publicAPI in any target child process such that
._runtime._async_main()
gets called / initialized correctly.
Obviously a lot more to go into in this section ..
The text was updated successfully, but these errors were encountered: