It's not generated because none of the python implementation actually uses it. So, generating it and including it in the egg would just increase the library size for everyone, when most people don't need it.
What makes you feel uncomfortable about generating it yourself? On Fri, Oct 1, 2010 at 6:01 AM, Louis-Marie <[email protected]> wrote: > Hi all, > > It looks like python installation of protocol buffers does not > generate the google.protobuf.compiler.plugin_pb2 python file, while > google.protobuf.descriptor_pb2 is explicitly generated by > protobuf/python/setup.py > > generate_proto("../src/google/protobuf/descriptor.proto") > > Shouldn't the plugin.proto file be compiled and installed the same > way? Maybe I am missing something there, be I feel very uncomfortable > recompiling it when I need to write a plugin. > > Thanks, > > Louis-Marie > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<protobuf%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
