[Fixed]-What is the difference between south migrations and django migrations?


South is a third part django app that added support for migrations before a builtin migration solution was introduced in Django 1.7. Unless you’re stuck with a long-dead Django version, there’s no reason you should use South at all. FWIW, just checking the south project’s page should have answered your question:

South has been deprecated.

From Django 1.7 upwards, migrations are built into the core of Django. If you are running a previous version, you can find the repository on BitBucket.

Feature-wide both are quite similar (which is not a big surprise since the new builtin migration system started it’s life as the 2.0 branch of South), except the new system works better, specially when you have to merge two branches each having it’s own migrations.

Leave a comment