Cannot Runserver After Django CircularDependencyError

Lets say you attempt a Django 1.7 migration and you get this error:

django.db.migrations.graph.CircularDependencyError

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.

 

Advertisements

One thought on “Cannot Runserver After Django CircularDependencyError

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s