-
Notifications
You must be signed in to change notification settings - Fork 565
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
Support generation of pyi files with py_proto_library #1293
Labels
Comments
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
friendly ping |
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 5, 2024
Protobuf team is taking ownership of `py_proto_library` and the implementation was moved to protobuf repository. Remove py_proto_library from rules_python, to prevent divergent implementations. Make a redirect with a deprecation warning, so that this doesn't break any users. Expected side effect of this change is also that the protobuf version is sufficiently updated that there is no more use of legacy struct providers. Closes #1935 Closes #1924 Closes #1925 Closes #1703 Closes #1707 Closes #1597 Closes #1293 Closes #1080 Fixes #1438
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🚀 feature request
Relevant Rules
New feature for
py_proto_library
Description
protoc
v3.20 and above supports to generate.pyi
files from protos. Whould be great ifpy_proto_library
would/could generate those as well by using the--pyi_out
argument toprotoc
.Describe the solution you'd like
A new attribute for
py_proto_library
to enable/disable the generation of.pyi
files and a way to reference them for packaging/editor support.Describe alternatives you've considered
Switching to https://github.com/grpc/grpc (which has added support here: grpc/grpc#32872), but we don't use grpc and would prefer to stick to primary bazel rules.
The text was updated successfully, but these errors were encountered: