>Any mechanism that caches in memory means that you'll have to do
>something fancy (or just restart your server) to ensure changes to
>templates are picked up. Why bother with this problem at all unless
>template performance becomes an issue?
Not really. What would be doable would be to use the c
On 4 Nov 2005, at 22:39, Brant Harris wrote:
The templates currently go through a seemingly needless two-step
process: compilation and rendering. It seems like the point would be
to compile once, and then not again until the template is changed.
So, what exactly the strategy on templates comp
Brant Harris wrote:
> Half way through ticket #603
> (http://code.djangoproject.com/ticket/603/) Robert brings up a topic
> of much interest to me, which is the templates and their compilation.
>
> The templates currently go through a seemingly needless two-step
> process: compilation and renderi
On 11/4/05, Brant Harris <[EMAIL PROTECTED]> wrote:
> Half way through ticket #603
> (http://code.djangoproject.com/ticket/603/) Robert brings up a topic
> of much interest to me, which is the templates and their compilation.
>
> The templates currently go through a seemingly needless two-step
> p
Half way through ticket #603
(http://code.djangoproject.com/ticket/603/) Robert brings up a topic
of much interest to me, which is the templates and their compilation.
The templates currently go through a seemingly needless two-step
process: compilation and rendering. It seems like the point wou
