interoperability with asyncio (part 1) #174
Merged
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.
This PR modifies the dispatch-py internals to build on the
asyncio
package in order to better integrate with frameworks like FastAPI, httpx, etc... and any other Python code that uses async/await constructs for I/O operations.A couple of notable changes:
async
, this is the only breaking changeIn a few places, we are constructing temporary event loops (using a class similar to
asyncio.Runner
) to convert from blocking to asyncio code, for example in the http server we use indispatch.run()
. This a bit hacky and probably not optimal, we could do better by taking a dependency onaiohttp
, I'll look into it in a follow up PR where I also want to investigate how we could integration the.dispatch()
method with asyncio.Fixes #122