Normally, in development with south. If the migrations get to the point were they're out of sync. The lead Dev removed the conflicting migrations and runs the schema migration command.
As for the django 1.7 flow of migrations, I cannot comment on it, but I would go into this problem with the assumption: I should be able to create an initial migration and go from there. One complication I see with this, is that only the django runtime knows about south which makes it near impossible to detect this in your packaging. My question now would be, can django migrations and south migrations co-exist and can I turn off django migrations? Cheers, -Joseph Curtin On Jul 24, 2014 1:27 PM, "Raphael Hertzog" <raph...@ouaza.com> wrote: > [ Please keep me in CC ] > > Hello, > > I'm one of the python-django Debian package maintainers and I have been > working on preparing the field for Django 1.7... and we have one problem > that we don't know how to handle. > > Consider that Debian contains Django but also Django applications using > South. When our users will upgrade from Debian 7 to Debian 8 > they will upgrade at the same time Django itself and the Django > applications. > > The new versions of the Django applications are likely to have unapplied > schema migrations managed by South but the system will have Django 1.7 > and we have no means to let the users apply those schema changes. > > I see two ways to go forward: > - either we find a way to apply South migrations with Django 1.7 > - or we enhance Django migrations to be able to tag some point > in the Django migrations as equivalent to some other point in the > South migrations, that way we can recreate the supposedly-unapplied > South migrations with Django 1.7 and mark those as unneeded if all > South migrations were already applied > > How can we solve this problem? > > Thank you for your help! > -- > Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer > > Discover the Debian Administrator's Handbook: > → http://debian-handbook.info/get/ > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-develop...@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/20140724202733.GA8255%40x230-buxy.home.ouaza.com > . > For more options, visit https://groups.google.com/d/optout. >
