Status Update
Comments
gh...@google.com <gh...@google.com> #2
Hello,
Thank you for reaching out to us!
My understanding of your case is that the dev_appserver is not considering the option provided through build_env_variables configuration which is part of the python3 app.yaml configuration. Please correct me if I'm wrong. I was not able to check content in google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/python/instance_factory.py:332 mentioned in description
But can you please check out this
—-
To run the dev_appserver.py tool, you must have a Python 2 interpreter of version 2.7.12 or newer installed on your machine (even if your app is written in another language or version, including Python 3).
—-
and let me know if this helps with the issue you are experiencing.
ii...@quickbase.com <ii...@quickbase.com> #3
Hi!
This doesn't have anything to do with the Python version I am running the dev_appserver on.
When you try to run a python3 application on the devappserver [e.g. application, which has runtime: python3xx
in it's app.yaml
], it creates a virtual environment on the fly for that python3 application, installing all it's dependencies in it.
When you try to do the same on GAE in production, you have control over the way pip is called through build_env_variables
in app.yaml
.
Unfortunately dev_appserver don't read those build_env_variables
and just calls pip without any options.
The impact may be seen in weird situations like the one described in this
And the way to work it around, is to provide pip with the --no-deps
options, which is not possible in dev_appserver now, as it doesn't speak build_env_variables
gh...@google.com <gh...@google.com> #4
Hello,
This has been forwarded to the Team so that they may evaluate it. Note that there are no ETAs for this issue. All communication regarding this is to be done here.
Thank you
Description
build_env_variables is part of the python3 app.yaml configuration. I am using it to provide pip with the --no-deps option.
The deployment of the service works as expected, considering the provided option and installing the dependencies without any issues.
The dev_appserver on the other hand is not considering the option in app.yaml, trying to install the dependencies without the --no-deps option and failing in my case, because of irrelevant to the problem circumstances.
What you expected to happen:
The dev_appserver to run pip with the additional options provided through the build_env_variables configuration.
Steps to reproduce:
See the contents in
google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/python/instance_factory.py:332
The options, provided by the app.yaml, should be added here.
Other information (workarounds you have tried, documentation consulted, etc):
I know that the build_env_variables are PRE-GA feature. I am dropping this bug report only in case this is a not-known issue, as INMO it is crucial for the option to get GA.