#25731: Remove choices from ether instance or method attribute in Select widget
-------------------------------------+-------------------------------------
Reporter: codingjoe | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Forms | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by codingjoe):
Tim, I could work on a patch, but I'd like to make a design decision
first.
As I see it, the only reason why there is the option to pass choices into
the renderer directly is the `ModelChoiceIterator`.
Where the regular choices get cast into a list, this would be a very poor
idea for the `ModelChoiceIterator`.
The question is, should we allow Widgets to be rendered multiple times and
drop the instance attribute, or should we not.
Another option would be to deepcopy the choices when they're being
rendered.
--
Ticket URL: <https://code.djangoproject.com/ticket/25731#comment:2>
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/067.a6f39274660a7aa74c5e47a11833faa8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
