On Tue, Sep 7, 2010 at 8:38 AM, Russell Keith-Magee <[email protected]> wrote: > Firstly, I'm not wild about "secure=request.validated". This looks > like a really simple way for people to say "secure=True" as a way of > "fixing" CSRF support that they can't get to work. The choice of > argument on the attribute isn't optional -- it *must* be > request.validated. So really, it's the request that is the argument > that needs to be passed in. The good news on this point is that a > "request aware form" is something that has been floated in other > discussions recently. I'll be sure to raise it at the DjangoCon > sprints this week as a topic for discussion.
After giving it a second thought on my ride to work I think request.is_valid() would be just as useful and would not require us breaching the form/request layer separation. -- Patryk Zawadzki -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
