#6652: Allow 'clean()' to specify the wrong field
---------------------------------------------------+------------------------
Reporter: Daniele Varrazzo <[EMAIL PROTECTED]> | Owner:
nobody
Status: closed | Component:
django.newforms
Version: SVN | Resolution:
wontfix
Keywords: feature | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------------------+------------------------
Comment (by Daniele Varrazzo <[EMAIL PROTECTED]>):
Replying to [comment:5 russellm]:
> My rejection of this idea was based on the fact that it introduces a
second way to raise field errors. However, I'm only a -0. Regardless,
better documentation of Form._errors is probably a good idea.
Are you sure exposing {{{Form._errors}}} is a good idea? Currently it is
an implementation detail (at least for people developing form logic):
exposing it in the API is an implementation leak that would tie the
current implementation to everybody's form logic.
Adding an optional field to the exception is a (mostly harmless) extension
of the current interface.
--
Ticket URL: <http://code.djangoproject.com/ticket/6652#comment:6>
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
-~----------~----~----~----~------~----~------~--~---
