Howdy folks, I was hacking around on a project, trying to use signals during model instantiation. I've used signals before, but came across an interesting 'wart' in the signals/dispatcher framework.
The end result is that a listener can become registered with the dispatcher more than once... thus triggering the same action twice. The problem doesn't look to be with PyDispatch, though... it seems to lie with the fact that imports can be from two locations (project_name.app_name.foo or app_name.foo). Using the latter approach (app_name.foo) seems to be popular for making apps portable... so I don't think discouraging it's use is a viable answer. [0] I also don't think I'm the first one to have stumbled across this. [1] I opened a ticket for the problem. [2] -- Ben [0] http://www.b-list.org/weblog/2007/03/27/reusable-django-apps [1] http://groups.google.com/group/django-users/browse_thread/thread/9fcf291064106519/7fa4a0eaf645d10e [2] http://code.djangoproject.com/ticket/3951 --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
