On Tue, Apr 28, 2009 at 12:31 PM, James Bennett <ubernost...@gmail.com> wrote: > > On Mon, Apr 27, 2009 at 10:49 PM, Tamas Szabo <szab...@gmail.com> wrote: >> I'm new to Python so I might not understand how keyword arguments work, BUT >> you do assume that authenticate will always be called with keyword >> arguments which isn't true. > > If you look at how django.contrib.auth.authenticate is implemented, > you'll see that it will *always* invoke the backend's authenticate() > keyword-style, which means an invalid argument set will *always* raise > TypeError.
OK, I missed that bit, sorry for that. You are right, the second issue isn't really an issue then. I still don't like that TypeError is silenced, but I will get used to it I guess :). Regards, Tamas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
