#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 Tim Graham <timograham@…>):
In [changeset:"24ebf17f04ee0ed157c430ff7d10ec0728abd48e" 24ebf17f]:
{{{
#!CommitTicketReference repository=""
revision="24ebf17f04ee0ed157c430ff7d10ec0728abd48e"
[1.9.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 df0a446fd4c864c003e4f941b5b7abd6f10c9427 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25510#comment:12>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.5f39299e70ddd66b99e05d834211502e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
