I'll agree that it isn't a code issue like models or admin classes which
don't validate. However it is a project state problem and is something that
users would probably want to know about regardless of whether they are
using runserver. There are other workflow issues that could be helped by
the ch
So, I don't think it should work within that framework, as having unapplied
migrations is not a _system issue_.
It's only really a helpful reminder that fits into the most common part of
the workflow (that being that you git pull, new migrations come in, and you
run runserver to check out the site
Last weekend I set out to fix https://code.djangoproject.com/ticket/21856
which was a 1.7 release blocker and holding up additional 1.7 testing for a
project
I'm currently working on. Upon diving in I saw that the checks for
un-applied migrations
were tied to the runserver command. I thought to
