> in fact, it takes us back to the > original proposal of a SafeForm that just takes the request object as > an argument to its constructor.
Well this seems much simpler, although there is still the requirement to add the csrf_fields whenever you write out the form in the template (which isn't much - I'm just looking for the shortest and most failsafe path). As for making a subclass - is there a problem having "request" as an optional field in the BaseForm constructor? It could then at least be included with as_table, etc automatically at the cost only of adding an extra constructor parameter to existing forms, and ignored without it. -rob --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
