Question :
This is the traceback on my windows system.
Traceback (most recent call last):
File "D:AMDworkspacesteelrumorsmanage.py", line 9, in <module>
django.setup()
File "D:AMDDjangodjango-django-4c85a0ddjango__init__.py", line 21, in setup
apps.populate(settings.INSTALLED_APPS)
File "D:AMDDjangodjango-django-4c85a0ddjangoappsregistry.py", line 108, in populate
app_config.import_models(all_models)
File "D:AMDDjangodjango-django-4c85a0ddjangoappsconfig.py", line 197, in import_models
self.models_module = import_module(models_module_name)
File "C:Python27libimportlib__init__.py", line 37, in import_module
__import__(name)
File "C:Python27libsite-packagesregistrationmodels.py", line 15, in <module>
User = get_user_model()
File "D:AMDDjangodjango-django-4c85a0ddjangocontribauth__init__.py", line 135, in get_user_model
return django_apps.get_model(settings.AUTH_USER_MODEL)
File "D:AMDDjangodjango-django-4c85a0ddjangoappsregistry.py", line 199, in get_model
self.check_models_ready()
File "D:AMDDjangodjango-django-4c85a0ddjangoappsregistry.py", line 131, in check_models_ready
raise AppRegistryNotReady("Models aren't loaded yet.")
django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.
And my manage.py looks like this:
import os
import sys
import django
if __name__ == "__main__":
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "steelrumors.settings")
django.setup()
from django.core.management import execute_from_command_line
execute_from_command_line(sys.argv)
I get this error when i am trying to use registration app in Django 1.7
Answer #1:
This is what solved it for us and these folks:
Our project started with Django 1.4, we went to 1.5 and then to 1.7. Our wsgi.py looked like this:
import os
from django.core.handlers.wsgi import WSGIHandler
os.environ['DJANGO_SETTINGS_MODULE'] = 'myapp.settings'
application = WSGIHandler()
When I updated to the 1.7 style WSGI handler:
import os
from django.core.wsgi import get_wsgi_application
os.environ['DJANGO_SETTINGS_MODULE'] = 'myapp.settings'
application = get_wsgi_application()
Everything works now.
Answer #2:
Running these commands solved my problem (credit to this answer):
import django
django.setup()
However I’m not sure why I need this. Comments would be appreciated.
Answer #3:
The issue is in your registration app. It seems django-registration calls get_user_module()
in models.py
at a module level (when models are still being loaded by the application registration process). This will no longer work:
try:
from django.contrib.auth import get_user_model
User = get_user_model()
except ImportError:
from django.contrib.auth.models import User
I’d change this models file to only call get_user_model()
inside methods (and not at module level) and in FKs use something like:
user = ForeignKey(settings.AUTH_USER_MODEL)
BTW, the call to django.setup()
shouldn’t be required in your manage.py
file, it’s called for you in execute_from_command_line
. (source)
Answer #4:
Just encountered the same issue. The problem is because of django-registration
incompatible with django 1.7 user model.
A simple fix is to change these lines of code, at your installed django-registration
module::
try:
from django.contrib.auth import get_user_model
User = get_user_model()
except ImportError:
from django.contrib.auth.models import User
to::
from django.conf import settings
try:
from django.contrib.auth import get_user_model
User = settings.AUTH_USER_MODEL
except ImportError:
from django.contrib.auth.models import User
Mine is at .venv/local/lib/python2.7/site-packages/registration/models.py
(virtualenv)
Answer #5:
This works for me for Django 1.9 . The Python script to execute was in the root of the Django project.
import django
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "PROJECT_NAME.settings")
django.setup()
from APP_NAME.models import *
Set PROJECT_NAME and APP_NAME to yours
Answer #6:
Another option is that you have a duplicate entry in INSTALLED_APPS. That threw this error for two different apps I tested. Apparently it’s not something Django checks for, but then who’s silly enough to put the same app in the list twice. Me, that’s who.
Answer #7:
Do you have a Python virtual environment that you need to enter before you run manage.py?
I ran into this error myself, and that was the problem.
Answer #8:
I ran into this issue when I use djangocms and added a plugin (in my case: djangocms-cascade). Of course I had to add the plugin to the INSTALLED_APPS. But the order is here important.
To place ‘cmsplugin_cascade’ before ‘cms’ solved the issue.