Hi,
Le 2017-11-10 à 08:50, guettli a écrit :
AFAIK django.setup() gets done implicit for web requests, you only
need to call it for scripts.
What do you mean with "when django.setup() is disabled"?
But maybe in my code base something works different than in standard
django. Up to now I thought we don't do special stuff there.
You don't need to call django.setup() unless your app is depending on
the django models.
This may reduce latency since initializing the whole django
infrastructure is expensive at runtime.
Etienne
<https://www.google.com/url?q=https%3A%2F%2Fbitbucket.org%2Ftkadm30%2Fdjango-hotsauce%2Fsrc%2F1cee385a8b7ecaf94c0e4c3785174aee43d72de2%2Flib%2Fnotmm%2Fcontrollers%2Fwsgi.pyx%3Fat%3D0.8-devel%26fileviewer%3Dfile-view-default&sa=D&sntz=1&usg=AFQjCNHYxgjPBcU31r96OObm4-IX-GtP0g>
--
You received this message because you are subscribed to the Google Groups "Django
users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/209cef25-c33a-c9ea-1654-caa04c89d2c1%40yandex.com.
For more options, visit https://groups.google.com/d/optout.
