python-betterproto
python-betterproto copied to clipboard
danielgtaylor
Clean, modern, Python 3.6+ code generator & library for Protobuf 3 and async gRPC
Version: betterproto==2.0.0b3 Requests with capital letters in the name seem to cause an issue with constructing methods. The request parameters are not added to the method. e.g proto file: ```...
Working with gRPC on `v2.0.0b3`, if the `.proto` package name starts with a capital letter, e.g. ``` proto package Echo; ``` Then the generated file becomes significantly different and invalid....
I feel that I use the plugin in a wrong way or there is something not designed correctly. example: I have directory with three files status.proto ``` message Success {...
Usage fails with BetterProto 2.0.0b4 Version ``` $ buf generate -vvv proto E0105 15:39:19.511094 1771702 template.go:991] created a body with 0 properties in the message, this might be unintended: name:"ModifyTileDisplayStateRequest"...
In the official implementation, Python modules are organized according to their location in the file system. If we follow this rule, it will be friendly to those migrating from then...
It would be nice if we could interact with a stream-unary endpoint by using a context-manager. currently the only way to send messages to a stream-unary endpoint is by using...
Google protobuf provides a library to parse and create text representations of messages, `google.protobuf.text_format` to be specific. I think it would be a good idea to add such module to...
I currently use the standard protobuf method `ParseFromString` quite a bit, but noticed that the generated `betterproto` dataclasses don't have this method, but they do have `SerializeToString` for compatibility. Is...
https://developers.google.com/protocol-buffers/docs/reference/csharp/class/google/protobuf/well-known-types/struct These should map to `dict[str, any]` and `any`
Metadata
Owner
Metadata
Clean, modern, Python 3.6+ code generator & library for Protobuf 3 and async gRPC