This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
[POC] - Implement run_in_process concept for trio
#1079
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pipermerriam
force-pushed
the
piper/trio-multiprocessing
branch
from
a26f138 to
99d193e
Compare
|
This now exists as part of https://github.com/ethereum/trio-run-in-process |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
I really want to move the process isolation out of the pluging API. This moves the logical location for running things in isolation to be via our service API.
How was it fixed?
This implements a
trio-basedrun_in_process(async_fn, *args)function which runsasync_fn(*args)in a separate process and returns the result.See: python-trio/trio#5
To-Do
Cute Animal Picture