Try looking at the code in the autodetector and doing some some debugging to figure out how old_field_dec and new_field_dec are different: https://github.com/django/django/blob/8db6a6c0a1c73bf08e71e00d4ab8c4af3c5f0cb8/django/db/migrations/autodetector.py#L911
On Monday, December 12, 2016 at 5:58:37 PM UTC-5, Francis Fisher wrote: > > On Wednesday, 30 November 2016 22:43:55 UTC, Mike Dewhirst wrote: >> >> On 1/12/2016 3:56 AM, Francis Fisher wrote: >> > Any idea why makemigrations would fail to recognise that a migration >> > has already been generated? >> >> I think migrations is seeing field choices differently each time it >> scans the model. Can you use a list rather than a tuple for choices? (Or >> vice versa - I don't remember) Or import the choices from another module? >> >> Thanks for this suggestion - I am using a field with choices somewhere in > the model referenced by a ForeignKey. > > I tried switching the choices from a tuple of tuples to a list of lists, > and I tried defining the choices in another module, I also tried entirely > removing the choices argument from the field definition, however none of > those actions resolved the issue. I've since tried this action with django > 1.10.4 but to no avail. > > -- 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+unsubscr...@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/375cbb28-97fa-45a4-9b64-ba1da95faa57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
