-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: generate python class interface from protobuf #476
base: master
Are you sure you want to change the base?
feat: generate python class interface from protobuf #476
Conversation
Command for generation with .pyi: python -m grpc_tools.protoc --proto_path=. --python_out=. --grpc_python_out=. --pyi_out=. ./pyzeebe/proto/gateway.proto
mypy-protobuf is more precise in the generated interface.
Hi. Why not fix it in |
…-python-class-interface-protobuf
The reasoning was that we could track changes more closely if we maintained it ourselves, which I think is even more important if we use the mypy option. Secondly, it's the interfaces for connecting to zeebe that we are programming against, especially when using typing. My understanding is that the interface belongs in the package itself. By the way, which version do you prefer, mypy or just the pyi? |
I think this package shouldn't be a part of pyzeebe:
|
Hello,
Kind Regards |
Description of PR...
Changes
proto
directory for protobuf and the generated stub and interface fileszeebe-grpc
API Updates
New Features (required)
Latest version of Zeebe API (GRPC) proto.
Command for generation with .pyi:
or with mypy
Deprecations (required)
Package
zeebe-grpc
is no longer used. And is removed rompyproject.toml
Removed all traces of zeebe-grpc and exchanged for the new stubs and interface files generated from
.proto
Enhancements (optional)
Now
.pyi
interface file is available and supports better type hints.Checklist
References
https://grpc.io/docs/languages/python/basics/#generating-client-and-server-code
https://mypy.readthedocs.io/en/stable/stubs.html
Resolves #475