21–30 of 84 posts
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
Are there any billing changes for apps previously running within the free tier in standard environment?
[1] You can use the free tier with the new Python 3.7 runtime.
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
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?)
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
Would the python3 runtime support things like ndb, taskqueue, memcache modules? We have a python2.7 standard app in production. It would be a considerable re-write if we had to move away from ndb and taskqueue.
it doesn't.
"The ndb ORM library is not available for Python 3. You can access Cloud Datastore through the Cloud Datastore API. You can use the Google Cloud client libraries to store and retrieve data from Cloud Datastore."
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
Would the python3 runtime support things like ndb, taskqueue, memcache modules? We have a python2.7 standard app in production. It would be a considerable re-write if we had to move away from ndb and taskqueue.
This means that if you already have a significant app running on Appengine Standard, none of the built-in APIs are supported (memcache, images, search, task queues, email, etc). That's a significant blocker to anyone wanting to upgrade their existing Standard 2.7 app to 3.7.
> At this time, the original App Engine-only APIs are not available in Second Generation runtimes, including Python 3.7. This means that if you already have a significant app running on Appengine Standard, none of the built-in APIs are supported (memcache, images, search, task queues, email, etc). That's a significant blocker to anyone wanting to upgrade their existing Standard 2.7 app to 3.7.
> At this time, the original App Engine-only APIs are not available in Second Generation runtimes, including Python 3.7. This means that if you already have a significant app running on Appengine Standard, none of the built-in APIs are supported (memcache, images, search, task queues, email, etc). That's a significant blocker to anyone wanting to upgrade their existing Standard 2.7 app to 3.7.
Correct, but for us (migrating from AE Flex to Standard) it meant that it was working out of the box.
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.
Out of curiosity, why did this take 10 years?
Long story short: security is hard. Launching these new unmodified Second Generation runtimes required us to develop new security and isolation technology (based on gVisor [1]). This allows us to securely run arbitrary code on shared data centers with isolation guarantees. This took us significantly longer than expected. The good news is, now that we have this new stack in place, we should be able to deliver runtime…
https://cloud.google.com/blog/products/gcp/open-sourcing-gvi...
That said, they don't quite go into the details of what type of isolation is missing from standard containers - I'm curious. It does seem like it would have been ideal for everyone if LXC would have had better isolation, rather than having to run a userspace kernel emulator thingy for each container, but c'est la vie!
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
I believe the title should be updated to say 3.7 as the article title does. The .7 is pretty significant to those who would be interested in this.
That may imply Python 3 earlier than 3.7 was on GAE, which is not the case.