-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
AttributeError: 'Credentials' object has no attribute 'authorize' #2832
Comments
To downgrade |
@dhermes this is why we released 0.21.1, right? |
@jonparrott beat me to it @Fkawala. I stupidly relesed #2828 will at least improve the messaging. |
This issue is present again with version |
@PLPeeters ditto ! |
+1 |
Resolves this issue: googleapis/google-cloud-python#2832 "AttributeError: 'Credentials' object has no attribute 'authorize"
I'm sort of caught between a rock and a hard place. 0.26.1 is not thread safe, but works sporadically. 0.27 seems to be thread safe, but has this issue inside of docker containers for some reason. I'll report more information once I figure out the exact issue. |
FYI it looks like the issue is caused by HAS_GOOGLE_AUTH being False:
It can be mitigated by running |
* feat: support more project_name specification locations for google credentials * refactor: use cloudvolume.secrets instead of reimplementing it * fix: trying to solve Credentials' object has no attribute 'authorize' googleapis/google-cloud-python#2832
Resolves this issue: googleapis/google-cloud-python#2832 "AttributeError: 'Credentials' object has no attribute 'authorize"
Hello,
To run this snippet :
Fails as follow
I test this in a fresh virtualenv whose freeze shows
pip show google-cloud-logging
showsand
pip show google-cloud-core
showsI do this test in a blank directory with only the json credentials and the above mentioned script. To run the snippet I do
GCLOUD_PROJECT=my-project GOOGLE_APPLICATION_CREDENTIALS=my-cred.json python snippet.py
Could it had something to do with the new version of
google-cloud-core
(0.22.0 published 2016-12-06) ?Bests,
François.
The text was updated successfully, but these errors were encountered: