I made this addition here:
https://github.com/django/django/commit/f8fdb7177b79b79968a3f40612d33c7367ae584f
I'm afraid most projects started before 1.4 will hit this :-/ but the fix is
really easy so I haven't tried to change the code.
--
Aymeric.
On 5 sept. 2014, at 20:23, Aymeric
Hi Robert,
The "old" version breaks because it's now missing a key part of the Django
startup sequence:
import django
django.setup()
This is something that was added in 1.7 as part of the app loading changes.
So, to answer your questions directly:
1) You either need to use
I ran into this problem myself upgrading to to django 1.7. The secret is
that get_wsgi_application calls django.setup() which is now required to
initialize django.
I went through and switched all my code to use get_wsgi_application().
get_wsgi_application() has been in the default wsgi.py in
I was using
import django.core.handlers.wsgi
application = django.core.handlers.wsgi.WSGIHandler()
as per whichever *This Is The Right Way To Lay Out A Django Application*
article I was reading at the time. This seems to now break in 1.7 (details
- from someone else - here
