Oops again... sorry for poor memory about the error message. Regarding the original issue -- in Claude's use case, he says that calling django.setup() before unpickling is not doable, as an external tool is doing the unpickling of model data. Should we say that unpickling model data from non-Django code is no longer possible?
On Tuesday, January 26, 2016 at 2:13:21 PM UTC-5, Aymeric Augustin wrote: > > On 26 janv. 2016, at 14:40, Tim Graham <timog...@gmail.com <javascript:>> > wrote: > > > Something like "Models aren't loaded yet. Are you missing django.setup() > in a standalone script?". > > > We’ve had this discussion before, cf. > 8121860be4b9379d107959290e5748bbaf6de1fe ;-) > > The exception message could point to the “Troubleshooting” section of > docs/ref/applications.txt. We could extend the explanation of what > constitutes a “standalone script” — many devs won’t expect celery / rq to > fall in this category. > > -- > 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/94ea6214-fb51-455b-8421-6ce7bb18c2e9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
