5 ms·

Notable omission of South ( http://south.aeracode.org/ http://south.aeracode.org/ )

by famousactress 13y ago

japhyr 13y ago
I think that's because South has been rolled into Django now. Is that correct?
- route3 13y ago
  Soon! Migrations[0] are being included in Django 1.7 which is currently under development. For those unaware, Andrew Godwin, the author of South, ran a successful Kickstarter campaign[1] the fund this effort to incorporate migrations in Django core. [0] https://docs.djangoproject.com/en/dev/topics/migrations/ https://docs.djangoproject.com/en/dev/topics/migrations/ [1] http://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django http://www.kickstarter.com/projects/andrewgodwin/schema-migr...
- huxley 13y ago
  Close, but not exactly, Andrew Godwin, the creator of South, has added support for migrations into the dev branch of Django, to be part of the Django 1.7 release. https://docs.djangoproject.com/en/dev/topics/migrations/ https://docs.djangoproject.com/en/dev/topics/migrations/ Andrew has significantly rethought migrations and applied the lessons he's learned from years of maintaining and developing South. He's kept a developer diary that has been pretty fascinating to read (YMMV): http://www.aeracode.org/2013/11/27/new-apps-migrations/ http://www.aeracode.org/2013/11/27/new-apps-migrations/ and others at: http://www.aeracode.org/category/django-diaries/ http://www.aeracode.org/category/django-diaries/ [update: route3 is faster than me, but still it's worth checking out the developer diaries]
  - ericd 13y ago
    For a greenfield app, would you recommend starting with 1.7, or do you think it will be simple enough to convert from South that it's not worth it? (I have no idea how stable 1.7 is)
    - jsmeaton 13y ago
      1.7 is still in development, but see the expected release schedule[0]. January 20th: 1.7 alpha March 6th: 1.7 beta May 1st: 1.7 release candidate May 15th: Final release (assuming a second release candidate is not needed) [0] http://python.6.x6.nabble.com/1-7-Release-Schedule-td5041311.html http://python.6.x6.nabble.com/1-7-Release-Schedule-td5041311...
    - huxley 13y ago
      Andrew has said in the past that his intent is to provide a migration path from classic South to "South 2.0" which will backport migrations to earlier versions of Django (versions 1.4-1.6, I believe) and also build on top of the migration infrastructure in Django 1.7. You should be fine sticking with South for now.
      - ericd 13y ago
        Cool, thanks very much to you and the other commenter.
- glynjackson 13y ago
  No, still use South everyday and will until it's rolled out in Django 1.7 - fingers crossed!

Notable omission of South ( http://south.aeracode.org/ http://south.aeracode.org/ )

japhyr 13y ago

I think that's because South has been rolled into Django now. Is that correct?

route3 13y ago
Soon! Migrations[0] are being included in Django 1.7 which is currently under development. For those unaware, Andrew Godwin, the author of South, ran a successful Kickstarter campaign[1] the fund this effort to incorporate migrations in Django core. [0] https://docs.djangoproject.com/en/dev/topics/migrations/ https://docs.djangoproject.com/en/dev/topics/migrations/ [1] http://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django http://www.kickstarter.com/projects/andrewgodwin/schema-migr...
huxley 13y ago
Close, but not exactly, Andrew Godwin, the creator of South, has added support for migrations into the dev branch of Django, to be part of the Django 1.7 release. https://docs.djangoproject.com/en/dev/topics/migrations/ https://docs.djangoproject.com/en/dev/topics/migrations/ Andrew has significantly rethought migrations and applied the lessons he's learned from years of maintaining and developing South. He's kept a developer diary that has been pretty fascinating to read (YMMV): http://www.aeracode.org/2013/11/27/new-apps-migrations/ http://www.aeracode.org/2013/11/27/new-apps-migrations/ and others at: http://www.aeracode.org/category/django-diaries/ http://www.aeracode.org/category/django-diaries/ [update: route3 is faster than me, but still it's worth checking out the developer diaries]
- ericd 13y ago
  For a greenfield app, would you recommend starting with 1.7, or do you think it will be simple enough to convert from South that it's not worth it? (I have no idea how stable 1.7 is)
  - jsmeaton 13y ago
    1.7 is still in development, but see the expected release schedule[0]. January 20th: 1.7 alpha March 6th: 1.7 beta May 1st: 1.7 release candidate May 15th: Final release (assuming a second release candidate is not needed) [0] http://python.6.x6.nabble.com/1-7-Release-Schedule-td5041311.html http://python.6.x6.nabble.com/1-7-Release-Schedule-td5041311...
  - huxley 13y ago
    Andrew has said in the past that his intent is to provide a migration path from classic South to "South 2.0" which will backport migrations to earlier versions of Django (versions 1.4-1.6, I believe) and also build on top of the migration infrastructure in Django 1.7. You should be fine sticking with South for now.
    - ericd 13y ago
      Cool, thanks very much to you and the other commenter.
glynjackson 13y ago
No, still use South everyday and will until it's rolled out in Django 1.7 - fingers crossed!