Right. This is indeed a case where the current state of the python tool is
bad.

On Jul 11, 2017 8:58 PM, "Sean Harger" <[email protected]> wrote:

> Nicolas,
>
> I knew that, but what I really am after is to be able to generate all my
> language targets from one binary. I have a project that includes both
> Python and Go code, and I want to generate all the GRPC stubs from one call
> to protoc. Is that possible without doing the process I suggested?
>
> Sean
>
> On Tue, Jul 11, 2017 at 12:23 AM Nicolas Noble <[email protected]>
> wrote:
>
>> The grpcio package contains a binary that is both protoc and the plugin,
>> all in one. So while it technically doesn't contain a binary called
>> "grpc_python_plugin", you don't need it when using the tools packages we
>> are providing. The point is that you don't need to have any hassle with
>> fiddling with the protoc options.
>>
>> As an easier comparison point, the nodejs tools package does this for you
>> for instance:
>>
>> https://github.com/grpc/grpc/blob/master/src/node/tools/bin/protoc.js
>>
>> As you can see, calling protoc with the nodejs package automatically
>> injects the plugin for you into the command-line, removing the need to even
>> know about the compiler plugin. This is true for any of the tools packages,
>> including python, which does it in a slightly more complicated way than
>> nodejs.
>>
>> On Mon, Jul 10, 2017 at 11:18 PM, Sean Harger <[email protected]>
>> wrote:
>>
>>> Is the only suitable way to obtain the grpc_python_plugin (for protoc)
>>> to build the library from source? That's what I am currently doing in my
>>> project and it seems like a waste of build time.
>>>
>>> All the evidence out there seems to suggest that installing grpcio from
>>> pip does not include this binary, and I cannot find any official
>>> alternatives other than downloading all of GRPC (and its dependencies) and
>>> building the grpc_python_plugin directly.
>>>
>>> Am I missing something?
>>>
>> --
>>> 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/CAGDDvkwNzV8cq2-2eQBYt6miWF0biXO_
>>> 0vY7ifmMpngyTBvwJw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/grpc-io/CAGDDvkwNzV8cq2-2eQBYt6miWF0biXO_0vY7ifmMpngyTBvwJw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/CAGDDvkwGqk85q2b1wzBbDuuq278_-7SWoZrQmGEwTK4ExbUkqg%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/grpc-io/CAGDDvkwGqk85q2b1wzBbDuuq278_-7SWoZrQmGEwTK4ExbUkqg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAOWnRi_s22sA_KDz6VSn%3D1bFEi%3DBWnZxJ7knEvc72-Nr5XqA9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to