django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

[qiailin]

I tried , the django version 1.10a1,1.10.5,1.103

django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

help, me ! thanks

[qiailin]

I'm looking for an asynchronous queue that is more suitable than celery but django_q is not available .

[jeroenbrouwer]

I'm getting the same error with django 1.11, are there any known causes for this problem?

[Eagllus]

I'm running Django 1.11 with Django-Q 0.8.0 and have no problems.
Could you provide some more information about your project?

[jeroenbrouwer]

Already fixed it by putting django_q below the app containing the settings and models in the INSTALLED_APPS setting. Maybe add this to the docs? 😄

[Eagllus]

@jeroenbrouwer not sure I understand what you mean.

In my settings I have

INSTALLED_APPS = (
    'django_q',
    'django.contrib.admin',
    'django.contrib.auth',
   ....
)

I even moved the INSTALLED_APPS to the beginning of my file.
could you share some information about the app your working on?

for example:

• how do you start your application?
• how is your configuration setup?

@qiailin did you every resolve this issue?

[jeroenbrouwer]

I've got quite an unusual setup for the models which caused the error. I've got a models app which imports the models from several files such that they are easily accessible throughout the whole application. This app needs to be loaded before django_q otherwise I get said error whenever I start django in whichever way possible: runserver, testserver, migrate etc.
And, I haven't had this problem with other external apps.

[Eagllus]

@jeroenbrouwer not sure if we can add anything about this to the documentation.
It sounds logical that importing your settings is something you want to be done at the top of your models app.

The error is triggered by calling Django-Q in this case before django.setup() is called.

[jeroenbrouwer]

@Eagllus I guess that's the case, but I'm failing to understand why the order of the loaded apps in the settings is important then...

[Eagllus]

In the INSTALLED_APPS it's not important but Django requires django.setup() to be ran before parts of an app can be called.
During the setup fase one important thing that it does is apps.populate(settings.INSTALLED_APPS)

def populate(self, installed_apps=None):
        """
        Loads application configurations and models.
        This method imports each application module and then each model module.
        It is thread safe and idempotent, but not reentrant.
        """

If you try to access an app before setup has run the function check_apps_ready will raise AppRegistryNotReady("Apps aren't loaded yet.")

[jeroenbrouwer]

@Eagllus I know this, just not sure why django-q has to be after my models app in the INSTALLED_APPS list 😉

It's working anyhow and it's doing its job like a charm!

[Eagllus]

@jeroenbrouwer I cant tell you without knowing any code 😉

But I'm happy to hear that Django-Q is doing a great job 😄

[stevemwangi]

Try activating the virtual env.

In my case, using git:

source scripts/activate
#Solves my problem.