On 18 déc. 2015, at 16:21, Tim Graham <timogra...@gmail.com> wrote: > Seems okay to me, but what about the point "It would also be useful to have > caching enabled in development so the template loading behaviour is (mostly) > the same in development as it is in production.” Would it be feasible to > always enable the cached template loader and control the proposed > "auto_reload" behavior using the value of DEBUG (i.e. no control over it in > OPTIONS)?
I was proposing to make the default more useful while keeping the option to configure template loaders explicitly because it seemed to give almost the same benefits with less effort. The proposed patch for auto-reloading doesn’t seem too bad in terms of complexity. Its main drawback is that it add a new auto-reload mechanism, distinct from django.utils.autoreload. I would prefer to trigger the autoreloader on template file changes to make it easier to switch e.g. to watchman in the future. That said, I swore I’d never touch Django’s autoreloader again except under duress ;-) -- 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/42025D6A-A876-4BBA-A389-146B512EB544%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
