I have a bunch of small apps on App Engine Standard, on the old generation Python 2 runtime. I'm itching to migrate to Python 3 Standard, but I use many of the classic App Engine APIs - datastore via ndb, task queues, memcache, etc - which are difficult to migrate away from <https://cloud.google.com/appengine/docs/standard/python3/python-differences#app_engine_apis> .
Tasks is one of the biggest current blockers. I'd happily switch to Cloud Tasks, but it has no local emulator, which makes local development and unit testing difficult at best. I've starred the issue. <https://issuetracker.google.com/issues/133627244> Any news on if/when we can expect an emulator? (I'd ask on the Cloud tasks mailing list <https://groups.google.com/forum/#!forum/gct-testers>, but it requires approval to join.) More broadly, the writing is on the wall. App Engine's future is serverless, containerized, and decoupled from services like datastore, task management, in-memory caches, etc. Flexible got there first, Standard's new generation of runtimes (Python 3 etc) followed. Other forum members have already written eloquently about this here (see GAE APIs <https://groups.google.com/d/topic/google-appengine/njsuyPxNtVY/discussion>, The end of PaaS? <https://groups.google.com/d/topic/google-appengine/DHMMv5r8qjU/discussion>), so I won't recap their concerns. Personally, I'm ok with this decoupling roadmap. I even trust that you all will gradually fill in our migration path. And I know Python 2 isn't going EOL anytime soon. I'm just impatient to get onto Python 3, so I'm chafing at blockers like Cloud Tasks' lack of an emulator. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b674ef4b-351b-49e8-9e2c-0ca0f61cb47d%40googlegroups.com.
