If I use ..
"runtime_config:
python_version: 3"
in app.yaml file, then the runtime config uses python3.6 by default. I
specifically want it to use python3.5.5 and not python3.6.
REF:
https://cloud.google.com/appengine/docs/flexible/python/reference/app-yaml
===
You can use the runtime_config
Figured out that GCP uses python 3.6 when python_version is set to 3 in
app.yaml
Changed the version to 3.5. Hopefully, this should solve some problems.
On Tuesday, July 31, 2018 at 10:10:33 AM UTC-7, eps...@gmail.com wrote:
>
> My GCP deployment was working fine until I did "gcloud components
GCP app has been deployed without any errors, but the runtime
configurations are not being considered.
I have the following runtime settings for python in app.yaml
runtime_config:
python_version: *3.5*
But I see this error:
Traceback (most recent call last):
File
Figured out that the GCP uses python 3.6 if the runtime config in app.yaml
is 3. My app uses python 3.5, there are some subtle differences between
python 3.5 and 3.6 that may be causing errors. 'python_version: 3.5' should
downgrade the runtime env
runtime_config:
python_version: 3.5
On
Did this issue get resolved? I see a lot of 502 Bad Gateway errors since my
last components upgrade ~ 2weeks.
On Friday, July 6, 2018 at 9:31:50 AM UTC-7, yi he wrote:
>
> Hello,
> I met a issue.
> Everything works fine at the begin of this week. In the middle of the
> week, user reported can
My GCP deployment was working fine until I did "gcloud components update"
two weeks ago. I understand that the command updates the libraries, and
there was an option to revert back to the previous version at the end of
the update, but I do not understand why there are so many
My GCP deployment was working fine until I did "gcloud components update"
two weeks ago. I understand that the command updates the libraries, and
there was an option to revert back to the previous version at the end of
the update, but I do not understand why there are so many
