undefined | Better HN

0 pointsStavrosK8y ago0 comments

I have a production Django application (the https://www.pastery.net pastebin). Just for fun, I'm going to change the container's image from python:3 to pypy:3 and document what happens here.

EDIT:

* Failed building psycopg2. Apparently I need to use psycopg2cffi instead. Retrying...

* manage.py now can't import Django. Hmm.

* Yeah, I have no idea why it can't import Django. I took most of the settings out of settings.py, thinking it somehow caused an ImportError, but it still fails. I think I have to give up at this point, as I have no more guesses.

* Turns out manage.py was trying to launch `/usr/bin/env python` and it needed `/usr/bin/env pypy3`. Seems odd to include a `python` binary on the image and not just alias it to `pypy3`, but it is what it is. Continuing...

Welp, everything seems to be running just fine. Here's the diff of all the changes I had to make:

https://www.pastery.net/rrjdfj/

Basically, install psycopg2cffi instead of psycopg2, use pypy3 for the interpreter instead of python, and add two lines to settings.py. All in all, pretty damn short!

0 comments

3 comments · 2 top-level

silviogutierrez8y ago· 1 in thread

Awesome investigation!

Any cursory benchmarks? Does it feel faster?

StavrosKOP8y ago

I couldn't tell you, really, as I'm just browsing on my local machine. It feels about the same, but I didn't expect to see much difference.

3131s8y ago

Thanks! I'll be doing this soon too then. Most of my apps don't rely on too many obscure packages and / or really large scientific computing packages, so I doubt I'll run into many problems either.

j / k navigate · click thread line to collapse