Re: Upgrade to Django 1.7 - AppRegistryNotReady exception

2014-10-13 Thread Carl Meyer
Hi Luca, To be clear, the call to ``django.setup()`` should be in the ``get_wsgi_application()`` function in the file ``django/core/wsgi.py``, which is part of Django, and you should not need to comment that out. It should not be necessary to have a call to ``django.setup()`` in your project's ws

Re: Upgrade to Django 1.7 - AppRegistryNotReady exception

2014-10-13 Thread Collin Anderson
Hi Luca, Yes, you have django.setup() commented out in your get_wsgi_application(). That is required. Collin -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to d

Re: Upgrade to Django 1.7 - AppRegistryNotReady exception

2014-10-12 Thread m1chael
after: os.environ.setdefault( add: import django django.setup() try that, let us know! ~mike On Sun, Oct 12, 2014 at 9:48 AM, Luca Trifilio wrote: > I'm struggling by trying to make things work after upgrading the Django > version from 1.6.7 to 1.7. It looks like I'm not able to focus

Upgrade to Django 1.7 - AppRegistryNotReady exception

2014-10-12 Thread Luca Trifilio
I'm struggling by trying to make things work after upgrading the Django version from 1.6.7 to 1.7. It looks like I'm not able to focus on the right matter. I try to resume the situation so far. Thing is: if I leave the command django.setup() in my wsgi.py file, when I try to access my website