Re: Django Migration File with Invalid import (import no longer exists)

Hi Ray,

Follow the advice at https://docs.djangoproject.com/en/stable/topics/migrations/#historical-models :

"To remove old references, you can squash migrations or, if there aren't many references, copy them into the migration files."

On Monday, December 5, 2016 at 1:22:15 PM UTC-5, Ray Leyendecker wrote:

I recently update the oauth2 library I am using in my project.

There are now import references in my (already run) migration files that no longer exist (as a result of the oauth2 upgrade).

As a result the make migrations command fails.

How is the best way to handle this problem?

I am also running my project on AWS (Amazon Web Services) so a solution that can be applied to that environment we be much appreciated.

Thanks 

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/acbdf956-8fcc-40dd-9b51-14d6b7dda847%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.