virtualenv python3 selection not taking effect in container

[Juan Uys]

Hello,

According to https://cloud.google.com/appengine/docs/flexible/python/customizing-the-python-runtime#selecting_the_python_version

I can tell virtualenv to use Python 3.5, but this doesn't seem to take effect after a gcloud deploy, judging by the stack trace.

Two tell-tale signs: "python2.7" in the trace, and failing on a Python3-style print statement ("SyntaxError: invalid syntax" in logs)

File "/home/vmagent/app/api/app.py", line 32: print('xxx', flush=True)

at import_app (/env/local/lib/python2.7/site-packages/gunicorn/util.py:352)
at load_wsgiapp (/env/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py:52)
at load (/env/local/lib/python2.7/site-packages/gunicorn/app/wsgiapp.py:65)
at wsgi (/env/local/lib/python2.7/site-packages/gunicorn/app/base.py:67)
at load_wsgi (/env/local/lib/python2.7/site-packages/gunicorn/workers/base.py:135)

What is the work-around? Is an old Docker layer being cached? How to force/clean it?

Thanks!

[Juan Uys]

Turns out the dropdown for the version in the log viewer was on a previous version, and it does in fact now use py3.6

[Yannick (Cloud Platform Support)]

Glad to hear you've resolved your issue. If in the future you come across some some behavior that looks like an issue with the platform, you can report it using our issue tracker.

[Juan Uys]

Thanks, Yannick. I've now learnt a new behaviour where I check the version drop-downs whenever I do anything on the console.

Perhaps the UI can flag a "(!) there's a more recent version", at least for newcomers.

On Wednesday, 23 August 2017 17:23:08 UTC+1, Juan Uys wrote: