its not the incompatibility of python (language/runtime), its missing services with regard to GAE Standard 2.7 and GAE Standard 3.0. (memcache, NDB, Search, Images, Users, webapp2, etc). Are these going to be duplicated in GAE3? and if so, will existing data and model definitions in the 2.7 datastore work in 3?
it looks like some work is being done for this but it would be great to know officially what Google plans for this upgrade process. how much code will need to change? https://github.com/googleapis/google-cloud-python/issues?q=NDB+sort%3Aupdated-desc also, generally what do you mean by "not directly affected on an immediate time frame"? a year, 2 years, 5 years before 2.7 apps stop running? On Wednesday, January 9, 2019 at 9:32:36 AM UTC-5, George (Cloud Platform Support) wrote: > > You are perfectly right, NP. Python 3 is made incompatible with 2, and > Python 3 does not support quite a few features, and will require effort to > re-program your app in an alternative manner. I was simply saying that > often the effort is not enormous, and becomes worthwhile on the longer > term. > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/8f45b06f-0852-4e46-9331-c3ebdbe3e481%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
