I have initially created the ticket https://code.djangoproject.com/ticket/25618 which addressed the bug that would occur if south migrations somehow ended up being still present in the migrations module.
According to a report in: https://code.djangoproject.com/ticket/25618#comment:7, this seems to break certain third party apps, in particular: * non-upgraded apps that retained south migrations in the migrations module but have not introduced Django migrations. An example of such an app is `django-extensions` Personally, I think, these apps haven't really supported Django past Django 1.6.x and if they claimed they did, it was a misconception on their part. However, in order not to break any apps that might have done this, I created a new pull request, that fixes this problem in a way that will not cause this issue. I wanted to check what people thought here regarding whether this should be incorporated or not? Should we make those apps fail and have them fully upgrade to support 1.7+, or should we address this and let them silently keep the south migrations? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. 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/99820cef-4404-40aa-97f8-4d3acace0a3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
