Why is django south not included in django.contrib?

Question

Possible duplicate:
Does core django support migration without a django-south application or similar?

django-south is the de facto standard for db migrations in django, and django itself does not support db migrations.

Now, since django contains some high-quality applications that almost should have in django.contrib , then:

• Why doesn't he include django-south?
• What are the thought processes behind this?
• Isn't that good enough or licensing issues?

Question on the topic:

• Does core django support migration without a django-south application or a similar application?

Answer 1

I remember watching a video where Jacob Kaplan-Moss answered this question. Although I cannot recall word for word, his answer was in order: they did not want to connect the South with the Django, since the South was still at a children's level and, by integrating the South at this stage, could slow its development.

Update 03/13. Andrew Godwin of Southern Glory kickstarted a database migration project built into the Django core. Expect this to land in Django 1.6 / 1.7.

Update 04/14 - Migration has become the core of Django 1.7. You can learn more about migrations @ https://docs.djangoproject.com/en/dev/topics/migrations/ .