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
Resolve python dependency patch in protobuf #14412
Comments
If the blocker is |
I think we also consume |
Happy to set up a branch on https://github.com/googleapis/python-api-common-protos with the |
These are all dependencies:
If we can remap these to pre-generated committed versions, that would probably work! |
cc @TristonianJones: we'd like to have google api expr Python protos published, instead of bazel build in googleapis. |
I created a branch on python-api-common-protos with the Releasing will need to wait for next year since I need to check that releasing these protos in this package is OK. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Not stale, but fell off my radar. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions. |
Complete the discussion in #14253 (comment).
The issue is conflicting python module definitions for
google.protobuf
andgoogle.rpc
undergoogle
coming from two repos, which requires patching in the module lookup code.cc @htuch
The text was updated successfully, but these errors were encountered: