On Sat, Mar 24, 2018 at 1:48 AM, Ben Slater <[email protected]> wrote:
> I am considering submitting a proposal for your summer of code idea > "Support static type-checking of both gRPC Python itself and of code that > uses gRPC Python" > Before I did so I was wondering if you could provide any further > clarification on what the project would involve, and what you would > consider a successful project to be. Have you reviewed other discussion on this mailing list about Google Summer of Code and about the pytype integration listed on our ideas page in particular? I suspect you'll find some of your answers there. A successful integration with pytype (or mypy; feel free to tell me I'm wrong in assuming pytype is the more suitable tool for gRPC Python) would be one that both (1) verifies that gRPC Python is free of the kinds of defects that pytype/mypy detects and (2) verifies that *applications that use gRPC Python* are free of the kinds of defects that pytype/mypy detects (at least with respect to their use of gRPC Python). Consider code that errantly passes a value that is not an iterator as the "request_iterator" argument to grpc.StreamUnaryMultiCallable.__call__ - we'd like the author of that code to know that that's a problem when they type-check their code rather than later when they run their code. -Nathaniel -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAEOYnASUcpNPZhdsZOTH-7kmgid%2B8wiQT40KVzE8%3DOJu6uG_qw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
