Why is django-south not included in django.contrib? [duplicate]

Question

Possible Duplicate:
Does core django supports migration without django-south or similar app?

django-south is a de facto standard for db migrations in django, moreover django itself doesn't supports db-migrations.

Now, since django carries some high-quality apps that are almost must haves in django.contrib then :

• Why doesn't it include django-south ?
• What is the thought processes behind that ?
• Is it not good enough or licencing issues ?

Related Question :

• Does core django supports migration without django-south or similar app?

Answer 1

I remember watching a video where Jacob Kaplan-Moss answered this very question. Whilst I can't remember the talk word for word, his response was on the lines of - They didn't want to bundle South into Django, as South was still in its infant stages and by integrating South at this stage would potentially slow down its development.

Update 03/13 - Andrew Godwin of South fame has kickstarted a project to get database migrations built into the core of Django. Expect this to land in Django 1.6 / 1.7.

Update 04/14 - Migration made it into the core of Django 1.7. You can read more about migrations @ https://docs.djangoproject.com/en/dev/topics/migrations/.