#22002: AppConfig.ready() and tests
--------------------------------------+------------------------------------
Reporter: mjtamlyn | Owner: zsiciarz
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: app-loading | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by jonash):
If it's not terribly difficult to implement then I'd like to advocate the
"explicit error" way of solving this issue. These kind of things are
easily overseen and difficult to debug and/or can cause severe damage in
your database. (People will abuse the `ready()` method for all kinds of
things you'd never dream about...)
--
Ticket URL: <https://code.djangoproject.com/ticket/22002#comment:8>
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.42d4303b3f8338bcd5fede150577c412%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
