GAE APIs

108 views
Skip to first unread message

Joshua Fox

unread,
Jan 28, 2019, 4:54:49 AM1/28/19
to google-a...@googlegroups.com
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.



George (Cloud Platform Support)

unread,
Jan 28, 2019, 1:58:36 PM1/28/19
to Google App Engine
Hello Joshua, 

You may check from time to time the official "Feature Deprecations" page. As you may realize, it is difficult to provide extra information, that is not officially published, over this special channel; also: fruitless to engage in speculation about deprecation dates that have not yet been published. 

Ryan B

unread,
Jan 28, 2019, 3:53:58 PM1/28/19
to Google App Engine
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) 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!

George (Cloud Platform Support)

unread,
Feb 20, 2019, 3:39:14 PM2/20/19
to Google App Engine
Hello Ryan, 

You are right, Python 2 to 3 code migration may be accomplished in part by employing tools such as modernize, futurize and 2to3, but the resulting, automatically converted code needs to be revised and in rewritten in places, as ambiguous semantic differences are to be expected. Your overall optimistic view on migration should prove in the end justified. 
Reply all
Reply to author
Forward
0 new messages