Will Pipelines and MapReduce libraries work on Python 3.7?

87 views
Skip to first unread message

Jacob G

unread,
Aug 8, 2018, 4:39:16 PM8/8/18
to Google App Engine
Will Pipelines and MapReduce libraries work on Python 3.7?

George (Cloud Platform Support)

unread,
Aug 9, 2018, 4:46:02 PM8/9/18
to Google App Engine
App Engine MapReduce is a community-maintained, open source library that is built on top of App Engine services and is no longer supported by Google. Cloud Dataflow, on the other hand, is fully supported by Google, and provides extended functionality compared to App Engine MapReduce. You are encouraged to migrate to Cloud Dataflow, if you did not do it already. 

The google-cloud-python libraries are supported on this runtime. You can use these libraries to access Google Cloud Platform services such as Cloud Pub/Sub, Cloud Datastore, Cloud Spanner and others. You can see the full list of supported products on the repository's README. More related detail can be gathered from the "Understanding differences between Python 2 and Python 3 on the App Engine standard environment" documentation page

Jacob G

unread,
Aug 9, 2018, 4:55:01 PM8/9/18
to Google App Engine
That will require a substantial re-architecture for many of your long-time customers who have built their business on GAE. Do you have a deprecation roadmap yet for the Python 2.7 runtime, as well as the various built-in services (e.g., memcache, gae sdk apis, etc.)?

George (Cloud Platform Support)

unread,
Aug 10, 2018, 12:19:29 PM8/10/18
to Google App Engine
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.  

bFlood

unread,
Aug 13, 2018, 12:37:39 PM8/13/18
to Google App Engine
"More related detail can be gathered from the "Understanding differences between Python 2 and Python 3 on the App Engine standard environment" documentation page. "

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? 

George (Cloud Platform Support)

unread,
Aug 13, 2018, 3:00:56 PM8/13/18
to Google App Engine
All these product deprecation deadlines are announced well in advance, allowing for what is usually considered enough transition time. If you would like to see related changes and improvements, you are encouraged to open an issue in the Public Issue Tracker. If you would like us to open this issue, you may write is in detail and submit it through a private message. You may write a private message using the drop-down menu offered by the "reply" button at the top-right of the editing window. 
It is impossible for us to predict how long Python 2.7 will be supported in future, as this depends on various factors and parameters, and of decisions out of my control. 
Reply all
Reply to author
Forward
0 new messages