Yeah, I do remember times where I had to put the signal handlers in the urls.py in order to lazyfy them, hence, avoiding the circle-dance. Of course, they would not fire via the management commands.
Ok, good to have the AppConfig.ready() for that. Thanks, Alight, Perhaps, I should create a ticket and enhancement for the documentation update. Thanks, Val On Tue, Feb 11, 2014 at 2:24 PM, Aymeric Augustin < [email protected]> wrote: > On 11 févr. 2014, at 20:20, Carl Meyer <[email protected]> wrote: > > > this documentation probably should be > > updated to recommend registering these signal handlers (and all other > > signal handlers) in the ready() method of an AppConfig, rather than as > > an import side effect anywhere. > > Indeed, that's the best practice as of Django 1.7. > > -- > Aymeric. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/8B2A0448-6CDA-457D-BF76-E7EBDD786A4D%40polytechnique.org > . > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CADy_H8F9%2BznkUKXK9m6gzkgh_bxLANLruBPv%2Bc4EtuogcGeLhQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
