That's an excellent point, Shai - if there are migrations they might be
essential to the app functioning. I think in that case we should not have
them work on 1.7 and up, and encourage people to send PRs to the apps
moving the directory name if it would work with syncdb.
Andrew
On Sat, Nov 7, 201
No, I think we can't do this generically.
If an app ships (South) migrations, we cannot assume that syncdb is an
adequate replacement; the migrations may include data-migrations which create
records the app needs. We could in general do something like, try to verify
that there are no data migra
I think if the fix is easy, we should continue to support them past 1.7,
since we're retaining syncdb support. However, if it's crazy complicated,
it's likely not worth it.
Andrew
On Wed, Nov 4, 2015 at 11:59 PM, David Filipovic
wrote:
> I have initially created the ticket
> https://code.django
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 seem
