#30505: Ordering of Field.choices is significant for makemigrations
----------------------------------+------------------------------------
Reporter: Marnanel Thurman | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Changes (by Carlton Gibson):
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
> I can put a test case together if you like.
Yes, please. Or a sample project that we can just run to play with.
(Pending that I'll assume it reproduces. 🙂)
I need to look deeper to see exactly what's going on here, but there's at
least a documentation issue:
> An iterable (e.g., a list or tuple) ...
If it's **required** to be ordered it should say `sequence` or similar.
I'd suspect it's just been assumed that a list or tuple would be used.
Maybe we can relax that. If not we'll have to change the docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/30505#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/066.40c532fa329145029a83bc09c27d463a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
