jonwayne
Joined 11 years ago
Karma
22
Submissions
16
Member since
Oct 9
github.com/jonparrott
View on Hacker NewsRecent submissions
Comment · 8 years ago
pipsi installs into isolated virtualenvs, then symlinks into `~/.local/bin` just like `pip install --user`. Combining pipsi for cross-project tools (tox, twine, nox, etc.) with pipenv for project-specific packages is all you need. You don't need to `pip install --user` some package at that point.
Comment · 10 years ago
(Not GP but also work on Python on GCP)
What was the specific Python 3 issue? I didn't see anything in your post specifically about Python 3.
Comment · 10 years ago
I am in Developer Relations so this is indeed part of my job. I'm glad we can be helpful.
Comment · 10 years ago
We are indeed working on creating a standalone Task Queues service that will work across all hosting platforms. You can sign up for the alpha here: https://goo.gl/Ya0AZd
(I work on the Python developer experience for Google Cloud Platform)
Comment · 10 years ago
Like Sublime.
Comment · 10 years ago
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
Note: I'm in Developer Relations for Google Cloud Platform
Comment · 10 years ago
Mozilla's websites notably use Python and Django.
Comment · 10 years ago
Re:
> Google App Engine's dev_appserver.py completely broke after an update, caused in part by another Google library being installed (protobuf...). Still not sure if the fix was rolled into a release yet...
We've been having a lot of fun with how tricky namespace packages are in Python. We've got a fix in for this issue that should hopefully be in the next SDK release, and we're looking into ways to better isolate dev_appserver from the OS environment.
A simple workaround is to activate an empty virtualenv before running dev_appserver.
Comment · 10 years ago
The whole "WSGI revision" effort is intended to solve the problem of websockets (and HTTP 2.0) across frameworks and servers.
Comment · 11 years ago
I wrote a flask extension that makes it a little easier to set these headers:
Comment · 11 years ago
Yes.
Comment · 11 years ago
Check out https://cloud.google.com/nodejs
Comment · 11 years ago
> I tried to move beyond archaic Java with managed VMs when they were first announced.
Please keep in mind that Managed VMs is still in beta, however, there are other parts of Google Cloud Platform that are in GA, including Compute Engine (IaaS), and Container Engine (somewhere between PaaS and IaaS). In fact, depending on how much control you want, Container Engine can be a better fit than App Engine.
Comment · 11 years ago
If you are a Java user and want to take advantage of Java 8, I really encourage you to check out managed VMs. We have a runtime available for Java 8 & Jetty 9 on github here: https://github.com/GoogleCloudPlatform/appengine-java-vm-run...
(disclaimer: I work for Google on Cloud Platform, but not on anything Java related)
Comment · 11 years ago
Absolutely not. You can use Cloud Datastore, or you can connect to any database that can communicate over sockets or http, including Cloud SQL. Of note is that Datastore has a free tier, Cloud SQL does not, and Socket usage can incur (some) cost when communicating with other databases.
I've seen many Python apps that connect to a free MongoDB instance hosted on Mongolab.
(also worth noting that Node.js support for App Engine is currently in beta.)
(disclaimer: I work for Google on Cloud Platform)