#24523: django.apps.registry.populate() does not handle failures in
app_config.ready()
-------------------------------+--------------------------------------
Reporter: kalium99 | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
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
-------------------------------+--------------------------------------
Comment (by aaugustin):
I'm not opposed to adding some strategically placed exception handling to
solve this but I'm afraid it isn't possible in general.
What if two apps provide `ready()` methods, the first one successfully
registers a signal and the second one fails? Re-running the app-loading
process will register the signal a second time, which could create a
variety of issues.
If we want to do this, we must require `ready()` methods to be idempotent.
--
Ticket URL: <https://code.djangoproject.com/ticket/24523#comment:6>
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/066.6a66e5651ae833876976e839389e0515%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
