#25634: AppRegistryNotReady Error upgrading from Django 1.8 to 1.9
-------------------------------------+-------------------------------------
Reporter: wide-awake | Owner: nobody
Type: Bug | Status: new
Component: Core (Management | Version: 1.9b1
commands) |
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
-------------------------------------+-------------------------------------
Changes (by claudep):
* status: closed => new
* resolution: invalid =>
* type: Uncategorized => Bug
* component: Uncategorized => Core (Management commands)
* stage: Unreviewed => Accepted
Comment:
I've had this same error in one of my projects, and I'd like to reopen it
because I think there is an exception swallowing which masks real errors.
(was related to django-reversion in my case).
With `runserver --noreload`, I'm getting the proper traceback which
reveals the real problem, but without the `--noreload`, I'm getting the
useless traceback mentioned by the reporter.
The problem is with this exception catching:
https://github.com/django/django/blob/stable/1.9.x/django/core/management/__init__.py#L315-L317
Frankly, I'd rather live with an autoreloader not restarting in case of
syntax errors (#24704) than with exception swallowing.
--
Ticket URL: <https://code.djangoproject.com/ticket/25634#comment:9>
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/068.7df64a0927d4c1fae12e938cea78cd65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
