Move JsonRPCServer.start_io
to high-level asyncio API
#506
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.
Description (e.g. "Related to ...", etc.)
Now that we have end-to-end tests around all 3 supported transports (stdio, tcp, websockets). This PR starts the process of migrating the
JsonRPCServer
side of pygls over to the high-level asyncio APIs.A new
pygls.io_
module has been introduced to hold the I/O code that's common between the client and server sides of pygls, includingrun
andrun_async
functions, which host the main sync/async message processing loopStdinAsyncReader
which allows a server to read from stdin asynchronouslyReader
andAsyncReader
typing protocols which capture the expected shape of the message source.The client's
start_io
andstart_tcp
as well as the server'sstart_io
methods have also been migrated to use the newrun_async
function.Code review checklist (for code reviewer to complete)
Automated linters
You can run the lints that are run on CI locally with: