Oops, here's the pull request: https://github.com/django/django/pull/6044
WIth the fix reverted and the missing django.setup() call, the exception is "django.core.exceptions.AppRegistryNotReady: Models aren't loaded yet.". I don't think we need a different exception in model_unpickle(), but maybe that message could mention a missing call to django.setup() as a common cause? Something like "Models aren't loaded yet. Are you missing django.setup() in a standalone script?". On Tuesday, January 26, 2016 at 7:53:05 AM UTC-5, Aymeric Augustin wrote: > > > > On 26 janv. 2016, at 09:57, Florian Apolloner <f.apo...@gmail.com > <javascript:>> wrote: > > > > Revert yes, but a check like that should stay and maybe raise an error > instead of calling apps.populate. > > > The following line, `apps.get_model(…)`, raises an exception when `not > apps.models_ready`. > > -- > Aymeric. > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/ec37323c-43f0-4e1f-8975-2b6835fc9820%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
