I came across a bug with an infinite loop in migration dependency
searching code. This is fixed here:
https://github.com/django/django/commit/ff3d746e8d8e8fbe6de287bd0f4c3a9fa23c18dc
(another person reviewing it would be good, though I think it is correct).
My question is, should we backport this to 1.7.x? For me, the bug
manifested itself with migrations that were automatically created by
Django itself, in a project with apps A, B, and C:
App B depends on app A
App A depends on app B (it didn't initially, but does now)
App C depends on one/both of them.
After doing makemigrations for A and B, makemigrations for C then went
into an infinite loop.
So this is not a really obscure case, and could affect a fair number of
people attempting to upgrade to Django 1.7, as I was.
Regards,
Luke
--
"We may not return the affection of those who like us, but we
always respect their good judgement." -- Libbie Fudim
Luke Plant ||
http://lukeplant.me.uk/