#14916: No proper initialization of models/signals/etc....
-----------------------------------------+------------------------------
Reporter: Pakal | Owner: nobody
Type: Uncategorized | Status: reopened
Milestone: | Component: Core (Other)
Version: 1.2 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------------
Changes (by anonymous):
* status: closed => reopened
* severity: => Normal
* resolution: duplicate =>
* easy: => 0
* ui_ux: => 0
* type: => Uncategorized
Comment:
I'm sorry, but this issue is not a duplicate of issue #3591 - which
doesn't deal with early import of models and signal setup.
Clearly at server startup, the first http requests are unlikely to trigger
the import of all install apps, so signals might be issued whereas all
their listeners aren't yet activated. Same for django models, whose
relationship tree won't be complete...
That's a serious workflow issue imo, invalidating the principle of the
signal system of django.
--
Ticket URL: <https://code.djangoproject.com/ticket/14916#comment:2>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
