#16663: Model field choices should accept empty iterator
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
danielnaab | Status: new
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Comment (by danielnaab):
I suspected there would be side effects of making the default
`self._choices == None` instead of the empty list, which is why I proposed
the simpler solution. A list-like object with length of zero is
functionally identical to an empty list, so I don't see what possible side
effects there could be to my suggestion (although setting choices to None
is more sensible in an absolute sense).
--
Ticket URL: <https://code.djangoproject.com/ticket/16663#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
