#3196: [design-q] [patch] Dynamically setting choices for a ChoiceField is
inconsistent
------------------------------------+---------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: defect | Status: new
Priority: normal | Milestone:
Component: django.newforms | Version:
Severity: normal | Resolution:
Keywords: newforms choicefield |
------------------------------------+---------------------------------------
Changes (by adrian):
* summary: [patch] Dynamically setting choices for a ChoiceField is
inconsistent => [design-q] [patch] Dynamically
setting choices for a ChoiceField is
inconsistent
Comment:
The current way it's handled is intentional -- a {{{Field}}} doesn't know
anything about the internals of its {{{Widget}}}. The {{{Widget.choices}}}
completely defines display, whereas the {{{Field.choices}}} completely
defines valid options. I agree that this can be confusing, but something
rubs me the wrong way about having a {{{Field}}} manipulate the internals
of its {{{Widget}}}.
I'm putting {{{[design-q]}}} in the ticket summary to designate "a design
decision needs to be made here."
--
Ticket URL: <http://code.djangoproject.com/ticket/3196#comment:>
Django <http://code.djangoproject.org/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
