Implement a new parameter to generate only async stubs #631
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 commit adds a new parameter
async_only
to the plugin, that when present, will only generate theasync
stubs.The current
{}AsyncStub
classes are fake, they are not present in the .py file, so they can only be used to write type hints. Using them also only works if the user manually casts the sync stub to theasync
stub.Since most users will only want to use either the sync or the
async
stub, this new parameter will allow generating only the stubs that are suited for the user's use case, and allow them to have less hacky code.Fixes #536.