#20569: Add cleaned_form to supersede cleaned_data
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Forms | Resolution: invalid
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 1
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by lukeplant):
* status: new => closed
* resolution: => invalid
Comment:
This would introduce massive backwards incompatibility, due to the
ambiguity of this in a template:
{{{
form.subject
}}}
This currently becomes `form['subject']` and accesses the bound field, but
with this change that would be shadowed by the attribute.
This is just asking for trouble, and an additional method to swap things
back is going to make things even more complicated and error prone.
Overall I think this is a worse API, especially once you've taken
templates into account, but either way the cost of the change far
outweighs any benefits from making it.
Therefore closing INVALID.
--
Ticket URL: <https://code.djangoproject.com/ticket/20569#comment:5>
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.aa49239cf056004b9791c7a60ea4abf8%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
