#29521: Infinite migrations without changes on code when Choices are store in a
dictionary
-------------------------------------+-------------------------------------
Reporter: Roberto Fernandez | Owner: nobody
Diaz |
Type: Bug | Status: closed
Component: Migrations | Version: 2.0
Severity: Normal | Resolution: invalid
Keywords: makemigrations | Triage Stage:
migration choices distionary | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Alexandr Tatarinov):
* status: new => closed
* resolution: => invalid
Comment:
First of all, you are using `set`, not `dict`. And order of elements in
both of them are not fixed. So I believe this is not a problem with
Django, store your choices in list or tuple as explained in documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/29521#comment:1>
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/071.0ef81c1851b2af7bb8bc1898434d0b86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
