Category archives: Pony

So somehow Django stopped being able to support .pyc files as migrations between our last builds with 1.11.lower and the current builds with 1.11.higher. Frozen environments use these to distribute just the .pyc (no source)... but somehow this got reverted because. But how did it get reverted in Django 1.11 (LTS) branch? Apparently it will ...

So it has taken far too long to get this done. As our migration operations were tightly coupled to South migrations, South was holding us back for far too long. Today I've pretty-much finished the migration. I wound up embedding a virtualenv inside the firmware for each product that has stub packages, the south migrations, ...

We embed Django in devices. There are 100s to 1000s of each device scattered around the world, each controlled by someone who may decide (for perfectly valid reasons) not to update one of those machines for years. Until now, we've used South migrations to allow a machine of any vintage to update to current release ...

So we have a lot of Django-based code where we'd like the user to be able to download a (subset of) the Django database as a "config file", then upload that "config file" to some number of other machines (or the original one), potentially long after the database has been migrated. I've got the skeleton ...

So I've been doing a spike test with a project where I'm trying to use React.js to build a front-end to a Django application. The bulk of this application is basic Django forms, posts, page-loads, etc. but there's a number of complex views for scheduling, content uploading etc. As of now I think I'm willing ...

As some may remember, one of our products involves the user posting very large (multiple GB) files. Previously we've been using an nginx extension that does a direct-to-disk streaming decode during an upload, but that extension isn't available in newer nginx (which we'd like to have available in order to take advantage of HTTP Live ...

Nginx has an upload module (in the nginx-extra package, not in the nginx-full one) that is very nice when you want to allow users to upload large files (think multi-GB video files).  The way it works is that you define a location to which posts may be made where the post may contain an upload. ...

We happened to be building a new build server today, and one of the steps in the process is to install packages.  We download all of the packages to local disk in one step (pip install --download ${packages}), then install them in the next step (pip install --no-index --find-links ${packages}).  Thing is, while pytz downloaded ...

So you added a totally cool and gnarly view that lets the user specify a POINT on a map (and text coordinates), and then two more to let them view and explore them.  Your users should love you forever... but those dratted users are complaining that the default location is off in the Atlantic ocean ...

A question was asked at the Django Toronto meetup during the metaclasses talk, basically, "what would you use this for"... so, here's my talk on Metaclasses [pdf] from a PyCon of the Python 2.2 era, which addressed that question at some length (the first half of the presentation). It doesn't secifically mention the use-case cited ...