#24521: frozensets don't seem to work quite right in migrations as field kwargs
----------------------------+---------------------------------------
Reporter: ris | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Keywords: migration kwarg frozenset
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------
Apologies if this is a rather sparse bug report, but I think it's quite a
straightforward issue to explain.
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.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/046.c98c586329a94892dc79361e8cb0676e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
