#25510: Putting invalid app name in INSTALLED_APPS makes runserver raise
django.core.exceptions.AppRegistryNotReady
------------------------------+------------------------------------
Reporter: sephii | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Comment (by aaugustin):
It can be considered a release blocker if it meets one of these conditions
— from https://docs.djangoproject.com/en/1.8/internals/release-process/:
> Security issues.
> Data loss bugs.
> Crashing bugs.
> Major functionality bugs in newly-introduced features.
If you think it does, feel free to toggle the flag again. (I would find
that advantageous because I could stop caring about this messy problem,
given that other people will pay attention in the run up to the 1.9
release.)
--
Ticket URL: <https://code.djangoproject.com/ticket/25510#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 [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.177d8be2fb4105f1e3ecdb9e5866a0fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
