#23112: Field.get_choices tries to index an iterable
-------------------------------------+-------------------------------------
Reporter: bernie_sumption | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7-rc-2
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by apollo13):
Replying to [comment:1 magopian]:
> Also, we can have a list of choices made of both named groups and
"normal" choices, so we might no "see" that the blank choice is defined in
the list of choices (it would be odd to not have it at the beginning of
the list, but i don't think it's required, at least from the previous code
and the docs).
That didn't work either previously, so we are somewhat safe in that
regard… The original iterable argument seems valid, we can just call list
on it I guess.
--
Ticket URL: <https://code.djangoproject.com/ticket/23112#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.355357bbb52b5edbb25404360903a95f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
