New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aio types] Fix some grpc.aio python types #32475
Conversation
|
Hi, thanks for the PR, the change looks fine to me except for one concern about changing |
Hello, thanks for taking a look. The Besides, if you look at the actual implementation of Now, as for what I'm trying to achieve: class FooServiceStub:
def __init__(self, channel: grpc.Channel) -> None: ...
GetFoo: grpc.UnaryUnaryMultiCallable[FooRequest,FooResponse] It generates non-aio stubs, true, but if you put |
Hi, sorry for late reply and thanks for the additional context. We agree with the proposed change, but we would like to verify that it does not break any In the meantime, please let us know if the change has already been tested. |
Hi, thank you. I'm already using this in some projects, but they are not open-source so I can't provide any examples unfortunately. |
Sorry about the delay. I just verified with both I added a small comment, can you help address that and fix merge conflict? Thanks again for the contribution! |
Hello, sorry for the long turnaround, but I added the |
Looks like some bazel tests are failing, you can check them locally using: |
With these, it is actually possible to have typed client stubs where the return type is correctly inferred. It's only for the non-streaming calls, because there is `RequestIterableType` for the streaming ones (but it's just Any with extra steps and would require much more work). --------- Co-authored-by: Xuan Wang <xuanwn@google.com>
With these, it is actually possible to have typed client stubs where the return type is correctly inferred. It's only for the non-streaming calls, because there is `RequestIterableType` for the streaming ones (but it's just Any with extra steps and would require much more work). --------- Co-authored-by: Xuan Wang <xuanwn@google.com>
With these, it is actually possible to have typed client stubs where the return type is correctly inferred.
It's only for the non-streaming calls, because there is
RequestIterableType
for the streaming ones (but it's just Any with extra steps and would require much more work).