Jacob Kaplan-Moss wrote: > Out of curiosity, did you consider having a single ``Form`` object > that may be bound or unbound? It seems like most of ``BoundForm`` > simply delegates down to the enclosed ``Form``, so perhaps ``Form.bind > ()`` should store the data internally and just behave differently > once bound?
+1, because I BoundForm's behavior is not so much different than Form's: the latter just has empty data and empty error dict but the main purpose is always the same: display a form. > This would likely result in code within ``Form`` like:: > > if self.is_bound(): > # whatever Looks like it can be useful for raising Exception when doing form.is_valid for an unbound form. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
