Fixture loading issues fixed
A regression in 0.8.3 meant that fixtures referring to models outside of the app they were in, and some other references to custom user models, were broken. This should now be fixed.
* A couple of issues with Django 1.6 have been fixed (including bad error handling and a loaddata incompatability)
* Migrations now import datetime from a special South module which provides the correct tz-aware or tz-naive version.
* A couple of issues fixed, including double-indexing errors, and correct persistence of non-unique indexes across ALTERs.
* The new localflavor fields are automatically accepted by the introspector.
* An issue with SQLite and default values that caused some migrations to fail has been fixed.
* South now recognises more Django MSSQL backends, and no longer fails to alter ForeignKeys that are in composite indexes.
* A small issue with the app cache on Django 1.6 has been fixed.
* The schemamigration and datamigration commands can now be properly inherited and their templates easily changed.
By sane, we mean that the status of every migration is tracked individually,
rather than just the number of the top migration reached; this means South
can detect when you have an unapplied migration that's sitting in the middle
of a whole load of applied ones, and will let you apply it straight off,
or let you roll back to it, and apply from there forward.
