On Friday 18 December 2009 01:44:05 Jeremy Dunck wrote: > On Thu, Dec 17, 2009 at 6:47 PM, Luke Plant <[email protected]> > wrote: ... > > > The problem with signals is that they don't return values, and so > > the mechanism can't interact with the actual login process. It > > can only notice that something is going on and try to stop it by > > some external mechanism. > > Actually, they do return values -- an iterable of (receiver, > response) pairs.
I had a suspicion that was the case, but couldn't find any examples of it in the docs. I guess the reason for the lack of examples is that in many cases it's kind of difficult to know what to do with the return values from a signal - what do you do with multiple values that contradict each other? But thanks for the correction. Luke -- "I'm at peace with the world. I'm completely serene. I know why I was put here and why everything exists. I am here so everybody can do what I want. Once everybody accepts it, they'll be serene too." (Calvin and Hobbes) Luke Plant || http://lukeplant.me.uk/ -- 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.
