Unfortunately, dev_appserver does not yet work with Python 3.x(See
https://cloud.google.com/appengine/docs/standard/python3/testing-and-deploying-your-app#local-dev-server).
You need to run it from a virtualenv which is running python 2.7.
Alternatively, as specified in
$ make serve
export
CLOUDSDK_PYTHON=/Users/dgaedcke/dev/client/nmg/nmg_payments_api/env/bin
dev_appserver.py --clear_datastore 0 --logs_path=/tmp/gaelogs
--log_level=warning \
--host 0.0.0.0 app.yaml
ERROR: Python 3 and later is not compatible with the Google Cloud SDK.
Please use Python
Could you paste the entire command surface?
Additionally, which version of Google Cloud SDK are you using?
On Tue, Sep 25, 2018 at 2:25 PM Dewey Gaedcke wrote:
> Thanks for the response and clarification!!
> I remember being told way back NOT to use venv with GAE & so all these
> posts where
Thanks for the response and clarification!!
I remember being told way back NOT to use venv with GAE & so all these
posts where it is now being shown is very confusing.
Using Py3.7, I'm now getting:
ERROR: Python 3 and later is not compatible with the Google Cloud SDK.
Please use Python version
Sorry for the confusion!
The vendored approach (installing into lib/ and adding an
appengine_config.py file) is correct for Python 2.7 on the standard
environment:
https://cloud.google.com/appengine/docs/standard/python/tools/using-libraries-python-27
Python 3.7 on the standard environment and
The amount of conflicting info about Python/GAE best practices is very
frustrating.
Can someone please clarify:
Should we use the vendored approach:
from google.appengine.ext import vendor
vendor.add('lib')
Or should we use VENV?
And is there a hybrid approach using both to accommodate most
