#13024: Signal sent on application startup
-------------------------------------+-------------------------------------
Reporter: wojteks | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version:
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Fixed on
Has patch: 0 | a branch
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Fak3):
Another issue, but related to this - where to bind signals?
Django documentation say that best place is put all bindings in the
signals.py and import your signals.py somewhere in models.py. But that
approach often results in circular import. Solving circuit is not always
possible. For example if in signal binding "sender" argument refers back
to model class.
Is there a ticket for signals issue? Is it worth to create one?
--
Ticket URL: <https://code.djangoproject.com/ticket/13024#comment:11>
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.
For more options, visit https://groups.google.com/groups/opt_out.
