On Sat, Mar 22, 2008 at 3:04 PM, Leo Soto M. <[EMAIL PROTECTED]> wrote: ... > On the other hand, all this gymnastic is done to allow receivers which > do not conform to the full API of a signal (i.e., does not accept all > signal arguments). What is the real reason behind this? Signal > "extensibility"?
Yeah, that's the idea. We're trying to keep some backwards compatibility, and the existing system provides that argument matching. Even some existing signal handlers in Django rely on it. Even so, it may be worth dropping. Numbers soon. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
