[Django] #23146: AppRegistryNotReady, translation bug when deploying with uWSGI

6 views
Skip to first unread message

Django

unread,
Aug 1, 2014, 3:28:42 PM8/1/14
to django-...@googlegroups.com
#23146: AppRegistryNotReady, translation bug when deploying with uWSGI
---------------------------------+--------------------------------
Reporter: joostvandorp@… | Owner: nobody
Type: Bug | Status: new
Component: Translations | Version: 1.7-rc-2
Severity: Release blocker | Keywords: uwsgi, translation
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------
When attempting to deploy Django1.7-rc-2 the error blocks the site from
loading every time.

"The translation infrastructure cannot be initialized before the "
django.core.exceptions.AppRegistryNotReady: The translation infrastructure
cannot be initialized before the apps registry is ready. Check that you
don't make non-lazy gettext calls at import time.

This is after starting a new project. No additional apps are created or
added.

--
Ticket URL: <https://code.djangoproject.com/ticket/23146>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Aug 1, 2014, 3:38:06 PM8/1/14
to django-...@googlegroups.com
#23146: AppRegistryNotReady, translation bug when deploying with uWSGI
------------------------------------+--------------------------------------
Reporter: joostvandorp@… | Owner: nobody
Type: Bug | Status: closed
Component: Translations | Version: 1.7-rc-2
Severity: Release blocker | Resolution: fixed

Keywords: uwsgi, translation | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by anonymous):

* status: new => closed
* needs_better_patch: => 0
* resolution: => fixed
* needs_tests: => 0
* needs_docs: => 0


Comment:

I always see the solution after reporting a bug.

The fix:

Change

module = django.core.handlers.wsgi:WSGIHandler()

to

module = django.core.wsgi:get_wsgi_application()

in the vassal.ini

--
Ticket URL: <https://code.djangoproject.com/ticket/23146#comment:1>

Reply all
Reply to author
Forward
0 new messages