#8663: Inconsistencies/Bug in ModelForm
---------------------------------------------+------------------------------
Reporter: lingrlongr | Owner: nobody
Status: closed | Milestone: 1.0
Component: Forms | Version: SVN
Resolution: wontfix | Keywords: ModelForm forms
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
After thinking about this a bit and trying out a couple of alternatives, I
think gkelly's summary is a fairly accurate statement of affairs. If
you're controlling things down to the level of the form widget, it's up to
you to pass in the choices you want: widgets display exactly what you give
them.
It would be nice in some cases to make it completely replaceable in the
way tried in the report, but it would be confusing and require working
around in other cases. So let's leave it as it is.
--
Ticket URL: <http://code.djangoproject.com/ticket/8663#comment:3>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
