Assigned
Status Update
Comments
ba...@google.com <ba...@google.com>
ku...@google.com <ku...@google.com> #2
mi...@gmail.com <mi...@gmail.com> #3
Hi, this error only affects Cloud SDK version 186. It was previously reported in Issue 72407295 and a fix for it should be released in Cloud SDK version 187.
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
In the mean time, you can downgrade to Cloud SDK version 185 as a workaround by running the following command:
gcloud components update --version 185.0.0
Description
As suggested by Google staff here:https://www.googlecloudcommunity.com/gc/Serverless/Is-it-possible-to-use-google-appengine-api-without-Python2-in/m-p/659306
I'm making this feature request to have support in local development environments using Python 3 (and without the need to have also Python 2) for all the functionality encapsulated within google.appengine.api (https://cloud.google.com/appengine/docs/standard/python3/reference/services/bundled/google/appengine/api )
It seems that if one wanted to build new apps using Python 3, it wouldn't be possible to use any of the functionality within google.appengine.api, and according to the error message one gets it seems to be related to the security model being different from the way it was when we used dev_appserver.py (i.e. Python2). Here's the error one gets:
google.appengine.runtime.apiproxy_errors.RPCFailedError: Attempted RPC call without active security ticket
I have tried to do things as explained in this page:https://github.com/GoogleCloudPlatform/appengine-python-standard
but no matter what I do, if I want to be able to use google.appengine.api in my dev. env., I have to run the app using dev_appserver.py and (at the time of this writing) that implies being anchored to Python2 although the rest of the application and everything else I do with Python works in Python 3.
Please, note that for many years I've been building apps around the functionality within that API (mail, memcache, taskqueue, etc.) and it would be a shame having to look for alternatives for all that if one wanted to move forward using newer Python runtimes.
Thanks.