Before you can run your app in the Python 3 runtime of the App Engine standard environment, you may need to change some of the configuration files that App Engine uses:
app.yaml. This file contains information about your app's code, such as the runtime and the app handlers.
appengine_config.py. The Python 2 runtime uses this file to access third-party libraries and provide values for constants and "hook functions". The Python 3 runtime doesn't use this file.
The behavior of some fields in your
file has been
modified. Remove any fields that are no longer supported and update other
fields as described in the following table.
|app_engine_apis||Applicable to Python 3 only||Required to be set to
|No longer supported||Not applicable in the Python 3 runtime.|
|threadsafe||No longer supported||All applications are presumed to be threadsafe. If your application isn't
|libraries||No longer supported||
|handlers: login||Supported if
||If you are not using the App Engine bundled services for Python 3, use Identity and Access Management (IAM) for user management.|
|handlers: script||Modified||In the Python 2 runtime, you use the
In the Python 3 runtime, you are required to use a web framework with
in-app routing (such as Flask or Django) instead of using the
To migrate your
Static file handling remains unchanged.
If you use any of the deprecated fields, App Engine returns an error when you deploy your app.
The Python 2 runtime in the App Engine standard environment uses the
This file is ignored in the Python 3 runtime. Instead, the Python 3 runtime
uses the standard
requirements.txt file to
including dependencies that use native code. For more information, see
in the Python 3 runtime.