On Sun, Aug 15, 2010 at 6:38 PM, DjangoRocks <ye.eug...@gmail.com> wrote: > I was wondering if South would be added as part of the standard Django > release?
Almost certainly not. However, I have spoken with Andrew about getting *parts* of South integrated into Django. If you dig into it, South really consists of three parts: 1) The core database abstraction layer, which allows you to issue a "change the name of this column" command (et al) without caring about database-specific eccentricities. This is a logical extension of the database abstraction layer that Django already provides. 2) Basic accounting of the migrations that have/haven't been applied on a given install. 3) Tools to automate the production of migrations and provide other rich migration services. Points 1 and 2 are ideas I'm interested in seeing in Django, and they form the simplest possible implementation of a migration tool. They are the common utilities that *every* migration tool needs to build, and there's very little benefit in having multiple implementations for these components. Point 3 is where South adds value. There are different ways to "discover" what migrations are required, and different ways to optimize the way migrations are written. The end goal would be to make South a set of tools that exploits the core functionality that Django's core provides. If you search django-dev, you should be able to find Andrew's proposal to implement this idea; whether it lands in Django 1.3 is entirely up to how much work gets done, and when it gets completed. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
