Python 3 on Google App Engine flexible environment now in beta

#1

Post by arouzrokh » Wed, Aug 10, 2016, 4:09 PM UTC

Python 3 on Google App Engine flexible environment now in beta
cloudplatform.googleblog.com

Re: Python 3 on Google App Engine flexible environment now in beta

#2

Post by jo909 » Wed, Aug 10, 2016, 4:41 PM UTC

I'm really glad this big fat blemish is now finally going away.

Anybody has a reasonable theory for why this took so long, despite users asking for it for years?

Re: Python 3 on Google App Engine flexible environment now in beta

#3

Post by daveguy » Wed, Aug 10, 2016, 4:45 PM UTC

jo909 wrote: post #2

I'm really glad this big fat blemish is now finally going away. Anybody has a reasonable theory for why this took so long, despite users asking for it for years?

I think you misread it. Unfortunately it looks like Python 3 is not going away. You did say big fat blemish, right?

Re: Python 3 on Google App Engine flexible environment now in beta

#4

Post by rch » Wed, Aug 10, 2016, 4:50 PM UTC

> you can use the tools and databases you already know and love

But not Postgres or Redis?

Edit: OK, I'm seeing some references in the docs. Still seems limited to deployment on generic instances though.

Re: Python 3 on Google App Engine flexible environment now in beta

#5

Post by advisedwang » Wed, Aug 10, 2016, 4:50 PM UTC

daveguy wrote: post #3

jo909 wrote: post #2

I'm really glad this big fat blemish is now finally going away. Anybody has a reasonable theory for why this took so long, despite users asking for it for years?

I think you misread it. Unfortunately it looks like Python 3 is not going away. You did say big fat blemish, right?

I think the "lack of Python 3 support" is the blemish referred to, not Python 3 itself.

Re: Python 3 on Google App Engine flexible environment now in beta

#6

Post by advisedwang » Wed, Aug 10, 2016, 4:51 PM UTC

rch wrote: post #4

> you can use the tools and databases you already know and love But not Postgres or Redis? Edit: OK, I'm seeing some references in the docs. Still seems limited to deployment on generic instances though.

You can absolutely use Postgres or Redis. If you spin them up on GCE you can connect to it from GAE Flexible. The only support lacking is a managed Postgres or Redis service like Cloud SQL does for MySQL.

Re: Python 3 on Google App Engine flexible environment now in beta

#7

Post by [deleted] » Wed, Aug 10, 2016, 4:54 PM UTC

advisedwang wrote: post #5

daveguy wrote: post #3

Earlier quoted context omitted.

I think you misread it. Unfortunately it looks like Python 3 is not going away. You did say big fat blemish, right?

I think the "lack of Python 3 support" is the blemish referred to, not Python 3 itself.

[deleted]

Re: Python 3 on Google App Engine flexible environment now in beta

#8

Post by dragonwriter » Wed, Aug 10, 2016, 4:55 PM UTC

jo909 wrote: post #2

I'm really glad this big fat blemish is now finally going away. Anybody has a reasonable theory for why this took so long, despite users asking for it for years?

> Anybody has a reasonable theory for why this took so long, despite users asking for it for years?

Well, initially, their investment in more runtimes was covering additional languages, not covering more versions of languages they already had. (IIRC, AE started with Python 2, added Java first, and then later Go and PHP.)

As that was happening, they gradually shifted focus from building out the old, fairly limited model of App Engine to building out other parts of the cloud platform, including (particularly relevant to future App Engine work) Compute Engine, to have a more robust cloud offering covering more use cases.

Then, they went back and returned to improving App Engine -- leveraging the now-broader cloud platform, and particularly Compute Engine -- shifting from the old model for new runtimes to the Flexible Environment (originally called "Managed VMs") model (built on Compute Engine, and which, in addition to including some additional Google-provided runtimes, means people can package up their own runtimes for App Engine).

Since doing so, they've released official Google runtimes for Python 3, Ruby (which people have been asking for longer than Python 3), and Node built on the Flexible Environment.

Re: Python 3 on Google App Engine flexible environment now in beta

#9

Post by jonwayne » Wed, Aug 10, 2016, 4:56 PM UTC

rch wrote: post #4

> you can use the tools and databases you already know and love But not Postgres or Redis? Edit: OK, I'm seeing some references in the docs. Still seems limited to deployment on generic instances though.

You can use Postgres and Redis. :) I'm working on writing new tutorials for both of those, but in the meantime:

You can host your own Postgres on Compute Engine [1] or use a hosted provider like ElephantSQL [2]. You can use whatever client library you want to connect to postgres in App Engine flexible.

Same story for redis - you can host it on Compute Engine [3] or use something like redislabs.

[1] https://cloud.google.com/solutions/set-up-postgres

[2] https://www.elephantsql.com/

[3] https://cloud.google.com/launcher/?q=redis

[4] https://redislabs.com/

Note: I'm in Developer Relations for Google Cloud Platform

Re: Python 3 on Google App Engine flexible environment now in beta

#10

Post by rch » Wed, Aug 10, 2016, 5:01 PM UTC

advisedwang wrote: post #6

rch wrote: post #4

> you can use the tools and databases you already know and love But not Postgres or Redis? Edit: OK, I'm seeing some references in the docs. Still seems limited to deployment on generic instances though.

You can absolutely use Postgres or Redis. If you spin them up on GCE you can connect to it from GAE Flexible. The only support lacking is a managed Postgres or Redis service like Cloud SQL does for MySQL.

Granted, but it still makes for a salient point when comparing RDS to GCE.