#9245: Using choices in a mode field forces use of TypedChoiceField in a form
field
-------------------------------+--------------------------------------------
Reporter: Tarken | Owner: badri
Status: reopened | Milestone:
Component: Forms | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-------------------------------+--------------------------------------------
Comment (by Skaffen):
Just a quick note: I've hit this issue for a different reason.
In my circumstance I'm passing in "choices" to a ManyToManyField
declaration (as I don't want to use a query to declare the choices) which
is leading to the model form setting the corresponding field up as a
TypedChoiceField. This, of course, has a single selection widget as its
default widget rather than multiple select.
--
Ticket URL: <http://code.djangoproject.com/ticket/9245#comment:7>
Django <http://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 [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
-~----------~----~----~----~------~----~------~--~---
