#10403: provide declarative syntax to define FormSets - including ModelFormSet
and
InlineFormSet
-------------------------------------+-------------------------------------
Reporter: Koen Biermans | Owner: nobody
<koen.biermans@…> | Status: new
Type: New feature | Version: master
Component: Forms | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: formset | Needs documentation: 1
modelformset inlineformset | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 1 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by carljm):
* stage: Design decision needed => Accepted
Comment:
The current factory-function implementation of formsets is unnecessarily
confusing to new users, and unlike anything else in Django. It can also
cause obscure issues with things that should "just work" (see e.g.
http://stackoverflow.com/questions/622982/django-passing-custom-form-
parameters-to-formset/624013#624013). It's ironic that we provide
declarative syntax for things like models and forms where it requires
metaclass magic, but in the case of formsets where a declarative syntax is
a simple matter of normal Python subclassing, we don't :-)
Haven't reviewed the latest patch in depth, but the broad strokes look
correct to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/10403#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
