On 2/3/06, hugo <[EMAIL PROTECTED]> wrote: > Or a way for the template loader to tell the machinery that the > template is already compiled? That way a template loader could cache > compiled templates and on access return the compiled template to > Django, instead of the template source? > > I would prefer it much if this template caching could be moved to the > template loader completely, because it's a much saner approach than > adding yet another setting - every setting makes the template system > more dependend on the settings and therefore makes more complicated to > separate it (to allow people to use the Django template system without > the rest of the machinery).
I think being able to edit/change templates without having to restart the Web server (in Apache's case) is a feature. :) And Fredrick came up with a really nice way of decoupling template settings in another thread. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
