-
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
gcloud-python can't import OpenSSL in App Engine (since it can't be vendored in) #1445
Comments
Moving this |
Re-opening, this is a different import error than the one in #1436, will rename accordingly |
Thank you for your clarification. 2016년 2월 12일 (금) 오전 1:03, Danny Hermes [email protected]님이 작성:
|
@savvykang-bnnjack Thanks for filing. For now, you can get around this by editing diff --git a/gcloud/credentials.py b/gcloud/credentials.py
index 9874042..ab5151c 100644
--- a/gcloud/credentials.py
+++ b/gcloud/credentials.py
@@ -19,7 +19,10 @@ import datetime
import six
from six.moves.urllib.parse import urlencode # pylint: disable=F0401
-from OpenSSL import crypto
+try:
+ from OpenSSL import crypto
+except ImportError:
+ crypto = None
from oauth2client import client
from oauth2client.client import _get_application_default_credential_from_file and then your code should work just fine using |
Good! |
I noticed the depending crypto module was changed since commit 948cccf. The project was deployed with GAE release 1.9.32 and gcloud-python 0.9.0.
Here are some context info according to your recent comments:
How do you vendor in gcloud-python for App Engine?
As described in GAE documentation: https://cloud.google.com/appengine/docs/python/tools/libraries27#vendoring
Which services / gcloud-python subpackages do you use? (I'm curious which imports / import paths your code has been using.)
I am generating signed url for an object in Google Cloud Storage. Here's the partial stacktrace:
I guess this is caused by the inherent inflexibility with runtime environment in GAE, and affects #1009 which seems to conflict with this issue.
The text was updated successfully, but these errors were encountered: