>> Python treats them as >> two different files, and hence the signal is attached twice.
> -> models.signals.post_save.connect(flaggedentry_post_save, > sender=FlaggedEntry) > Or is there likely to be something else we've got wrong > in our app? > Well, just in case - watch out for the dispatch_uid kwarg to connect(). This can be used to quietly prevent double signal registrations from the same connect() running twice: models.signals.post_save.connect(flaggedentry_post_save, sender=FlaggedEntry, dispatch_uid='mofin.store.models') - it'll then only register the signal once even if the module is loaded twice, inadvertently or otherwise, since the connect() sees the same dispatch_uid both times. I've found a useful place to put signal registrations is django app dir __init__.py file. Otherwise they're sometimes not found until a bit late, but each app's __init__.py is hit quite early on (so long as they're in INSTALLED_APPS I guess) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
