Conversation
0x676e67
added
the
C-refactor
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In this refactoring, all blocking API implementation types have been moved to the python.blocking package for access and use. The
BlockingStreamertype has been removed, and theStreamerobject type is now reused to implement both synchronous and asynchronous iterators.The
BlockingClient,BlockingResponse, andBlockingWebSockettypes have been renamed toClient,Response, andWebSocket, respectively.Although these names are the same as those in the async API implementation, there is no conflict, since the blocking API can be accessed through the
blockingmodule.