Thanks for supporting this cutting edge technology. I really hope it catches on.
I can't tell if you're sarcastic or not. Python 3 is pretty old now, definitely not cutting edge technology.
Python 3 is now available on App Engine standard environment
61–70 of 84 posts
Re: Python 3 is now available on App Engine standard environment
#62Thanks for supporting this cutting edge technology. I really hope it catches on.
I can't tell if you're sarcastic or not. Python 3 is pretty old now, definitely not cutting edge technology.
Pretty sure they're being sarcastic. But I'm guessing the commenter hasn't used Google Cloud anyway - Python 3 was supported on Flex enviroments for a long time. The news here is that they're supporting it on Standard environments, and there seems to be good technical reasons for taking so long.
Re: Python 3 is now available on App Engine standard environment
#63Earlier quoted context omitted.
The (datastore) client libraries take up the http request quota and the build-in mechanism of the Standard Environment is not. Google recommends going forward with client libraries everywhere in the documentation but what's the solution on the introduced request limitation which isn't mentioned anywhere? (Or is this finally fixed in the meanwhile?)
I'm not aware of this issue. Can you point me to a public bug/GitHub issue?
We hit that HTTP request limit as well, and (driven by a discussion with Google support) migrated our backend away from the REST-based Google Cloud Datastore API to the internal (ApiProxy-based) Appengine API. Reduced the latency as well. I can send you the internal support ticket nr if interested.
Re: Python 3 is now available on App Engine standard environment
#64Earlier quoted context omitted.
It is not possible to access Postgres based CloudSQL from Python on AppEngine standard. See here: https://cloud.google.com/sql/docs/postgres/connect-app-engin... Note that only node and Java are listed under non-Flex. I got burned by this and had to start over with MySQL.
> It is not possible to access Postgres based CloudSQL from Python on AppEngine standard. It is possible on the new (beta) Python 3. 7 runtime on AppEngine standard: https://cloud.google.com/appengine/docs/standard/python3/usi...
If you're an existing AppEngine standard user/customer, it's pretty likely that that means you will not be able to take advantage of PostgreSQL, as the new runtime does NOT give you access to a ton of their existing services that you are probably already using (such as datastore.)
Re: Python 3 is now available on App Engine standard environment
#65Earlier quoted context omitted.
I'm not aware of this issue. Can you point me to a public bug/GitHub issue?
We hit that HTTP request limit as well, and (driven by a discussion with Google support) migrated our backend away from the REST-based Google Cloud Datastore API to the internal (ApiProxy-based) Appengine API. Reduced the latency as well. I can send you the internal support ticket nr if interested.
Sure, feel free to send it to me directly. stewartr at google.com.
Re: Python 3 is now available on App Engine standard environment
#66Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
Does this means, DJango can be supported natively ?
Re: Python 3 is now available on App Engine standard environment
#67Re: Python 3 is now available on App Engine standard environment
#68Earlier quoted context omitted.
> It is not possible to access Postgres based CloudSQL from Python on AppEngine standard. It is possible on the new (beta) Python 3. 7 runtime on AppEngine standard: https://cloud.google.com/appengine/docs/standard/python3/usi...
If you're an existing AppEngine standard user/customer, it's pretty likely that that means you will not be able to take advantage of PostgreSQL, as the new runtime does NOT give you access to a ton of their existing services that you are probably already using (such as datastore.)
Hi optimusclimb -- just want to make clear that using Cloud SQL to connect to PostgreSQL should work using Python 3.7 on the App Engine standard environment. Your earlier comment accurately pointed out a gap in our docs. We're going to address that -- thank you.
If you try Cloud SQL and find that it doesn't work with PostgreSQL on this new runtime, that's a bug and we need to fix it.
Re: Python 3 is now available on App Engine standard environment
#69We're a SaaS platform running on App Engine and were part of the early-access program. Porting over our Python 3 based platform from App Engine Flex to AE Standard took just a few hours - only tweaks needed were to the YAML config files and rewrite our deployment scripts after creating a new environment and project. We still maintain a docker-based environment on AWS EBS which we were able to port over as well. Overa…
Just curious, why did you migrate from Flex to Standard? Only for the 10X price/performance boost for infrequently accessed services?
PS: Regarding automagically handling spikes I have a warning that might be useful for you. The way AE load balancer works is that it:
0. A request comes.
1. AE checks for available instance. If none available:
2. Spins up new instance.
3. !!! Assigns the request to that instance.
4. Waits for /_ah/warmup to finish.
5. Adds that instance to its serving pool so other requests may be routed there as well.
Note that step 4 is after step 3, so at least one request will wait for /_ah/warmup. So occasionally you will see requests with high latency (if your warmup is slow, of course). Our latency requirements were quite high, so we ended up switching to manual scaling and heavily over-provision to handle spikes. That costed us good money, though.
Re: Python 3 is now available on App Engine standard environment
#70Earlier quoted context omitted.
Correct, but for us (migrating from AE Flex to Standard) it meant that it was working out of the box.
It seems to me this product is mainly targeted at 1) new customers, and 2) AE Flex customers wanting to switch to Standard. The third category (Existing 2.7 Standard customers wanting to just upgrade to 3.7 -- which is me unfortunately) are going to be disappointed and stuck in a hard place, I think.
What would be the incentive to migrate from AE Flexible to Standard if these apis are not there? The only thing I can think of is scale to 0.