Lets say you attempt a Django 1.7 migration and you get this error:
Well that sucks.
In my case, the model change was of minor importance and I did not have time to figure out how to resolve the circular dependency. So I reverted all changes and moved on. But now “runserver” fails with the circular dependency error. Somehow the error persists after the code is reverted. How does this happen?
Turns out that makemigrations creates a folder called “notmigrations” in the folder that contains your project. Delete this folder and you will be back to the initial state.