"More related detail can be gathered from the "Understanding differences 
between Python 2 and Python 3 on the App Engine standard environment" 
documentation page. "
https://cloud.google.com/appengine/docs/standard/python3/python-differences#cloud_client_libraries

based on that doc, I don't think a year will be enough?!? I think you owe 
it to many of your longtime GAE developers to produce both short term and 
long term roadmaps for the python2.7 runtime. will there be wrappers for 
all of the existing GAE services? (ndb, users, memcache etc)? if not, how 
long can we realistically expect 2.7 to be supported? 





On Friday, August 10, 2018 at 12:19:29 PM UTC-4, George (Cloud Platform 
Support) wrote:
>
> Hello Jacob, 
>
> It is difficult to predict such things as deprecation deadlines, as they 
> depend on various factors such as requests from Customers, market outlook, 
> actual needs and implementation of new features to replace the old. In any 
> case, you should not worry as long as no public announcement is made. In 
> all similar cases from the past, public announcements were made no less 
> than a year in advance, so you can be sure that Python 2.7 won't be 
> declared as obsolete before at least one year from now on; more precisely 
> at least one year from the date of the future announcement. These long 
> delays are offered for the precise reasons you mentioned: the substantial 
> effort to re-create and adapt your apps to the new environment. This 
> applies in a similar way to the various built-in services you refer to.  
>

-- 
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/a1bb5dbb-691d-4914-8301-0f1b5860fa35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to