#24523: django.apps.registry.populate() does not handle failures in
app_config.ready()
--------------------------------------+------------------------------------
Reporter: kalium99 | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
Replying to [comment:13 aaugustin]:
> I think we must require ready() methods to be idempotent. Strictly
speaking this is backwards-incompatible. But it's also a good property.
Ouch. That's quite a painful requirement, actually, given that e.g. we
recommend registering signal handlers in `ready()`. I really think
imposing an idempotency requirement on `ready()` must be a last resort, if
there's any possible way Django could avoid double-calling it instead.
--
Ticket URL: <https://code.djangoproject.com/ticket/24523#comment:14>
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.3b73c748b949c203697486c20c3a82da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
