Using django 1.7.7, a custom model field returning a {{{frozenset}}} as a
value in the {{{kwargs}}} dict from {{{deconstruct}}} will cause
{{{makemigrations}}} to seemingly coerce this value to a tuple. Because
this tuple does not exactly equal the frozenset, this trips up
{{{makemigrations}}}' change detection logic, and this will get detected
as a "change" each and every time {{{makemigrations}}} is run for
eternity.
Use of a {{{set}}} however works as expected, so this is a bit odd.
--
Ticket URL: <https://code.djangoproject.com/ticket/24521>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* has_patch: 0 => 1
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
PR here: https://github.com/django/django/pull/4387
--
Ticket URL: <https://code.djangoproject.com/ticket/24521#comment:1>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/24521#comment:2>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"1aadade373336c3f534986cdcc0ba33714d85c8e" 1aadade]:
{{{
#!CommitTicketReference repository=""
revision="1aadade373336c3f534986cdcc0ba33714d85c8e"
Fixed #24521 -- Added support for serializing frozensets in migrations.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24521#comment:3>