Upgrading Django

October 14, 2016

For the second time in a few years I've found myself doing a number of Django upgrades. It's a good thing: I'm happy the framework I chose to base most of my work on when I went solo has stayed relevant. But this time I wanted to document some of the pain points to make things easier on anyone else going through the same.

First off, this round of updates has been a lot easier than the first: back then I was the point of contact for WebFaction clients who had a Django app but no longer had a developer and those orphaned projects trended ancient. I started working with Django in 2009 with Django 1.1 and that was modern compared to most of the WebFaction projects. The biggest challenge in that group was a project running on 0.96 and using psycopg. I'd been installing psycopg2 for so long at that point it never occurred to me there was a version before it. And the Internet felt the same way: obtaining a version of Django that old was a challenge (see this thread for how to get versions no longer listed in Pypi). Obtaining a copy of psycopg proved impossible (I cheated and wound up downloading the folder from the client's site-packages directory and using that to replicate the issue they were seeing-- definitely not a recommended approach).

General Guidelines

Version-Specific Notes









Previously: Debugging a Vue.js Error | After this: A Dog Who's Lost Its Bite | All Posts
Tagged: django