#5174: Formsets - is_valid() crashes unbound forms
---------------------------------------------------+------------------------
Reporter: Simon Litchfield <[EMAIL PROTECTED]> | Owner:
adrian
Status: closed | Component:
django.newforms
Version: newforms-admin | Resolution:
duplicate
Keywords: | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------------------+------------------------
Changes (by jkocherhans):
* status: reopened => closed
* resolution: => duplicate
Comment:
Duplicate of #4867. It may seem meaningless to call is_valid on an unbound
form, but that's how Form behaves. Consistency wins here. If anyone wants
to argue that both situations should raise something like an
!UnboundError, please bring it up on django-dev.
--
Ticket URL: <http://code.djangoproject.com/ticket/5174#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
-~----------~----~----~----~------~----~------~--~---
