put an upper bound on bigquery #2007
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
google-cloud-bigquerypackage recently got upped to1.23.0, which has an implicit dependency onsix>=1.13.0. Unfortunately,google-cloud-bigquerydoesn't specify asixversion, and its dependencygoogle-cloud-coreonly specifiessix>=1.10.See the issue here: googleapis/google-cloud-python#9965
This PR both explicitly requires
six>=1.13.0to resolve the hidden dependency.This also excludes newer versions of
google-cloud-bigquery/google-cloud-corethan what's out there to hopefully avoid any new surprises.Unfortunately this will only fix
0.15.1and up, but that's really all we can do unless we want to cut a0.14.5.