This repository has been archived by the owner on Nov 29, 2023. It is now read-only.
fix!: update package names to avoid conflict with google-cloud-bigquery #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the
google.cloud.bigquery
path as aplain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
This PR was generated using Autosynth. 馃寛
Synth log will be available here:
https://source.cloud.google.com/results/invocations/efdacdcf-4630-4d74-9bea-5ef6df381d38/targets
PiperOrigin-RevId: 339531446
Source-Link: googleapis/googleapis@ab0498d
PiperOrigin-RevId: 339048690
Source-Link: googleapis/googleapis@3c8c2d8
PiperOrigin-RevId: 338646463
Source-Link: googleapis/googleapis@20b11df
PiperOrigin-RevId: 327026955
Source-Link: googleapis/googleapis@0dc0a6c