On Wed, Mar 1, 2017 at 8:41 AM, Leonardo Romor <[email protected]> wrote:
> Same problem here, the _pb2_grpc.py is generated in a folder of my project > toghether with the _pb2.py. > The _pb2_grpc.py tries to import the _pb2 from the python path (ie: import > generated.interface_pb2 as generated_dot_interface__pb2) > You may wish to subscribe to issues 9450 <https://github.com/grpc/grpc/issues/9450> and 9575 <https://github.com/grpc/grpc/issues/9575> which I suspect are related to this. Let me ask of you the same question I ask in 9450 <https://github.com/grpc/grpc/issues/9450#issuecomment-282377998>: given that we have test coverage of our code generation <https://github.com/grpc/grpc/blob/master/src/python/grpcio_tests/tests/protoc_plugin/_split_definitions_test.py> that runs and passes with Python 3 <https://grpc-testing.appspot.com/job/gRPC_master_linux/>, what's wrong with our test? What's the smallest code-and-instructions corpus you can share with us that demonstrates the problem you're having? If you are finding that generated code works with Python 2 and fails with Python 3, are you able to recommend a fix that would preserve the "same code is generated for both Python 2 and Python 3" property in place today, or would you recommend that different code be generated for different Python versions? -N -- 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/CAEOYnASthgTNhvEv3bvXRsPJzcJX%2B6i%2B9km_xac4WsvObbG1ZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
