This seems to be expected behavior, "In other words, your applications’
root packages and the modules that define your application configuration
classes shouldn’t import any models, even indirectly." from
https://docs.djangoproject.com/en/1.8/ref/applications/#how-applications-are-loaded
You
In DAL we mostly moved autocomplete_light/__init__.py to
autocomplete_light/shortcuts.py, and we're trying to make a fuss about
it on internet so that users using google before opening issues find
it :D
It would be great if other libraries used the same renaming for the
sake of consistencies
Hello all,
I'm not sure if it's expected behaviour, so I thought I'd rather report
this here: I've had issues importing multiple (well[ish]-known) 3rd party
apps with Django 1.9 that import fine on Django 1.8. The error I'm getting
is AppRegistryNotReady, caused by some (indirect) import to