Django custom user models, South, and reusable apps

Kevin Dias
Mon, 26 Aug 2013 00:00:00 -0700
writing

While working on django-chalk I ran into an issue with the way South migrations and Django 1.5's custom user models can interact. South examines your models when you create a migration and then stores them as a hard-coded dictionary inside the migration. This is fine when you know that models will be identical wherever your migration is run, but if you're writing a reusable app that isn't always an assumption you can make.