stewart27

5 ms·

1.
by stewart27 7y ago
I think you can force cold starts between your tests by re-deploying your function/container. You could (optionally) leave a small buffer (<1 minute) after the deployment to ensure that traffic has fully migrated.
2.
by stewart27 7y ago
+1 You can also set up Cloud Scheduler to push to Pub/Sub, which can trigger your function. This is helpful if you don't want your function to be available via a public HTTPS endpoint.
3.
by stewart27 7y ago
Cloud Functions PM here. Your intuition around concurrency is correct: Cloud Functions has "per instance concurrency" of 1. Cloud Run lets you go significantly higher than that (default 80). This means that our infrastructure will
4.
by stewart27 8y ago
Indeed. If you want to compile the binary yourself/don't want to upload source code, we have a serverless containers product currently available as an early preview (sign up at g.co/serverlesscontainers). This would allow you
5.
by stewart27 8y ago
If you're interested in something along the lines of the latter, you can sign up for an early access preview here: g.co/serverlesscontainers
6.
by stewart27 8y ago
It's definitely something that we've discussed. Would you consider running a container that could be run like Cloud Functions? This container could run the binary that you create. It's not something that we support today but
7.
by stewart27 8y ago
> I'm curious how the implementation of Go has affected the ease of integrating other languages. In some ways, it helps. You start to see similar issues arise and know what to look out for when you're launching a new runtime. I
8.
by stewart27 8y ago
While I can't share details publicly, I can confirm that we're actively working on new runtimes and performance improvements.
9.
by stewart27 8y ago
Which ones would you like to see? We're always looking for new use cases to support.
10.
by stewart27 8y ago
Cloud Functions PM here. I can give some insight: * We've been running a private early access preview/alpha since last August. * This was our first compiled language on Cloud Functions, which came with its own set of challenges. *
11.
by stewart27 8y ago
You're not wrong. Cloud Functions Product Manager here. We've been running a private early access preview since we first showed this at GopherCon in August. I'm really happy to see this first step but we have a lot of work ah
12.
by stewart27 8y ago
The Google Cloud client libraries [1] are fully supported. You can use these to access services like Datastore, Spanner, Natural Language, and many other Cloud services. They work on this new runtime, on the flexible environment, on a VM, y
13.
by stewart27 8y ago
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
14.
by stewart27 8y ago
Yes, Django and Django 2.0 (which only supports Python 3) should work.
15.
by stewart27 8y ago
Sure, feel free to send it to me directly. stewartr at google.com.
16.
by stewart27 8y ago
They're both available as early access previews. You can request access via the sign up forms.
17.
by stewart27 8y ago
Thanks for noticing this. We'll get this updated.
18.
by stewart27 8y ago
This is supported today! https://cloud.google.com/functions/docs/writing/
19.
by stewart27 8y ago
You would use Cloud SQL to access PostgreSQL. Here's how you configure your App Engine standard environment project to use Cloud SQL: https://cloud.google.com/appengine/docs/standard/python3/usi...
20.
by stewart27 8y ago
We're working on suitable replacements for these services. In some cases, e.g., Cloud Tasks, we're pretty close. Others will take a little longer. We'll share updates as we make more of these services available.
21.
by stewart27 8y ago
I'm not aware of this issue. Can you point me to a public bug/GitHub issue?
22.
by stewart27 8y ago
There are no changes to the free tier[1] or to apps running using the existing Python 2.7 runtime in the standard environment. [1] You can use the free tier with the new Python 3.7 runtime.
23.
by stewart27 8y ago
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 c
24.
by stewart27 8y ago
Yes, this runtime supports arbitrary dependencies specified via a `requirements.txt` file. If you find a library that doesn't work, please let us know. In general, anything that works using an open source Python 3.7 distribution should
25.
by stewart27 8y ago
Hi all, Product Manager for App Engine here. Happy to answer any questions about Python 3 on the App Engine standard environment.
26.
Python 3 is now available on App Engine standard environment(cloud.google.com)
277 points by stewart27 8y ago|79 comments
27.
by stewart27 8y ago
Python 3.7 on the App Engine standard environment was announced today but not yet released to the public. We'll have more to share soon.
28.
by stewart27 8y ago
Hi lazypenguin -- in case you're still interested in Python 3 support on App Engine -- we're working on it. If you'd like to be included in a private alpha test, please complete this form: https://docs.google.com&#
29.
by stewart27 8y ago
Hi, I'm a Product Manager on the App Engine team. We're actually (finally!) gearing up to offer Python 3. Would you like to be an alpha tester? Here's the sign-up form: https://docs.google.com/forms/d&#x2