Skip to content

BUG: #10652 google-api-python-client minimum version check #10656

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

Closed

Conversation

fdellavedova-zz
Copy link

Fixes bug with version check for google-api-python-client

@jreback
Copy link
Contributor

jreback commented Jul 23, 2015

this is not tested on travis, not really sure how to evaluate this.

cc @jacobschaer
cc @sean-schaefer

@fdellavedova-zz
Copy link
Author

What do you mean? it seems the tests passed . Am I missing something?

@jreback
Copy link
Contributor

jreback commented Jul 23, 2015

and they pass on current master (w/o this change). So you will have to show an environment that fails first.

@fdellavedova-zz
Copy link
Author

to replicate:

$ pip install google-api-python-client==1.2.0

and then:

>>> from pandas.io import gbq
>>> gbq.read_gbq('foo', 'spam')
....
ImportError: pandas requires google-api-python-client >= 1.2.0 for Google BigQuery support, current version 1.2

@jreback
Copy link
Contributor

jreback commented Jul 23, 2015

gr8. so modify one of the ci environments to load that version. have it fail and then use your change to have it pass. It is run in ci/requirements-2.7.txt now.

@jacobschaer
Copy link
Contributor

I remember this issue... seems a shame to have to resort to using regular expression matching. @parthea mentioned using StrictVersion instead of LooseVersion might resolve the issue - I haven't really looked into the differences, but his example in the discussion for: #10857 seems to suggest it will work.

@jreback jreback added this to the 0.17.0 milestone Sep 13, 2015
@jreback
Copy link
Contributor

jreback commented Sep 13, 2015

replaced by #10857

@jreback jreback closed this Sep 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants