#9605: form.save() exceptions should be more informative
-----------------------------------------------------+----------------------
Reporter: [EMAIL PROTECTED] | Owner: nobody
Status: closed | Milestone:
Component: Uncategorized | Version: 1.0
Resolution: wontfix | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Changes (by mtredinnick):
* status: new => closed
* resolution: => wontfix
Comment:
This isn't worth it -- it provides more than one way to do something. The
errors are already available on the form instance at that moment (via
`self.errors`) and if you want to throw away the form before checking the
exception, you have to handle it yourself. Subclassing !ModelForm and
providing a wrapper that raises the exception you want seems like one
solution there.
All your explanation of how POST and GET, etc, should be done is very
normal and not relevant here. The only piece that seems relevant is that
you don't access the form instance (it's difficult to tell from your
example where the form handling is done, since it's all in the
decorators). Since it's easy enough to do so (whatever one of your
decorators is handling the form can take care of that), Django doesn't
need a change to accommodate this.
--
Ticket URL: <http://code.djangoproject.com/ticket/9605#comment:3>
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 django-updates@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
