#25510: Putting invalid app name in INSTALLED_APPS makes runserver raise
django.core.exceptions.AppRegistryNotReady
-------------------------------------+-------------------------------------
Reporter: sephii | Owner: nobody
Type: Bug | Status: closed
Component: Core (Other) | Version: 1.8
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"9ccb92ad0130c0fc5fec43d3b914b49df688ffa5" 9ccb92a]:
{{{
#!CommitTicketReference repository=""
revision="9ccb92ad0130c0fc5fec43d3b914b49df688ffa5"
[1.8.x] Fixed #25510 -- Allowed runserver to start with incorrect
INSTALLED_APPS.
In that case, the content of INSTALLED_APPS will be ignored until it's
fixed and the autoreloader kicks in. I confirmed this behavior manually.
As explained on the ticket it's hard to write a test for this case
Backport of df0a446f from master.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25510#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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.825da8b6d74cbb72c17bc2f63f785564%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
