Hello, Acoordint to the official documentation [1] "Starting on January 1, 2020 <https://www.python.org/doc/sunset-python-2/>, the Python community will no longer update, fix bugs, or patch security issues for Python 2.7. We recommend that you migrate apps that are still running in the Python 2 runtime of the App Engine standard environment to the Python 3 runtime as soon as possible"
Also [2] "AppCfg is a utility command that is included in the deprecated App Engine SDK <https://cloud.google.com/appengine/docs/standard/java/setting-up-environment#appengine_sdk> . We recommend that you replace your use of AppCfg commands with gcloud commands, which is part of the Cloud SDK <https://cloud.google.com/appengine/docs/standard/java/setting-up-environment> " Therefore you application will continue to work but it might have unexpected issues. ------------------- [1]. https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3 [2]. https://cloud.google.com/appengine/docs/standard/java/tools/migrating-from-appcfg-to-gcloud On Thursday, August 13, 2020 at 3:50:23 AM UTC+2, MVI Solutions wrote: > > Hello everyone, > > One of our projects uses Memcache, Mail API, Task Queue, Cloud KMS V1, and > other legacy app engine services for Python 2 (standard env). If we can > build this project with gcloud, will this continue to work after August 30 > (after appcfg build tool shutdown)? > > > We really need this to know for one of our clients. > > > Thanks > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/61823a66-fdcf-499d-8c59-28349e7b3ac1o%40googlegroups.com.
