On Sep 17, 3:42 pm, Simon Willison <si...@simonwillison.net> wrote: > All good points - the change in function signature naturally fell out > of the CSRF work (since the form needs access to the request object in > both cases) but you've convinced me that it's a step too far - I'll > see if I can fix that.
I just pushed a new release which changes the constructor signature back to the way it works in regular Django: http://pypi.python.org/pypi/django-safeform/2.0.0 (Really should have used 0.1 / 0.2 etc for the version numbers, lesson learnt for next time!) I also added some unit testing sugar to address one of Luke's (many) points, see the "Unit testing" section of the README file. I'm still digesting the rest of his e-mail, plenty to think about there. Cheers, Simon --~--~---------~--~----~------------~-------~--~----~ 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 django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
