#22029: documentation: new best place to put the signal handler registration
--------------------------------------+------------------------------------
Reporter: un33k | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"994274ea8315282484bc24aa403b2fd12b5bdeec"]:
{{{
#!CommitTicketReference repository=""
revision="994274ea8315282484bc24aa403b2fd12b5bdeec"
[1.7.x] Fixed #22029 -- Removed obsolete advice on registering
migrate/syncdb signal handlers.
All signals should now be registered in AppConfig.ready().
Thanks un33k for the report.
Backport of 5233b36693 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22029#comment:7>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.75ecc050a2c3cd127b31ce8df1ef69f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
