When I created my initial branch for this, it was easy enough to auto reload a file once it changed, but it was difficult to deal with template directory precedence. For instance, if `admin/base.html` was cached, but a custom `admin/base.html` was added in a loader or directory with higher precedence, the cached version was still used. My concern is that it's not clear to the user they need to restart the process to see the new template. A similar situation happens when templates are deleted.
I can see why some people would still want the ability to turn this feature on anyway, but without a solution for the above cases it seems better to me as an opt-in rather than a default. -- 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/65d011fc-469c-4244-925d-ce8b2cc5a80d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
