this is the existential question facing app engine's glacier-under-the-surface installed base of python 2 apps. the writing seems to be on the wall for the legacy, custom app engine python APIs; all signs point to the decoupled, REST-based APIs to standalone services (datastore, cloud tasks, etc) as the future.
you're right, though, we still haven't heard a migration path for long time users like us with existing python codebases that use the old APIs. word on the street seems to be that google knows this, and has been thinking about an answer for a while. one obvious reason is that there are plenty of big whale app engine customers in the same boat as us (ahem <https://www.snap.com/>) who presumably have more leverage. i have no inside knowledge, but my bet is that we'll get some form of compatibility layer, either porting (most) old libraries to use the new REST APIs under the hood, and/or (less likely) a code transformation tool like python's 2to3. i doubt either one would handle 100% of existing code, but if they hit 80% or 90%, i expect they'd declare victory. here's hoping! On Monday, January 28, 2019 at 1:54:49 AM UTC-8, Joshua Fox wrote: > > Are there end-of-life plans for GAE APIs in GAE Standard Environment, as > indeed happened in Flexible Environment already? > > If so, what is the timeline? > > -- > > > *JOSHUA FOX* > Director, Software Architecture | Freightos > > > > *T (Israel): *+972-545691165 | *T (US)*: +1-3123400953 > Smooth shipping. > > > > -- 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/561c5a7a-414b-4601-a680-4df119bd437d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
