Re: Make template caching a feature of the Django template engine

Hi everybody, Tim pointed me to this discussion here and I support the overall goal. It accelerates development, especially when designing somewhat prettier Web pages. Quoting my quite naive approach from the issue tracker (https://code.djangoproject.com/ticket/26507#comment:2): """ I don't

Re: Make template caching a feature of the Django template engine

On 18 déc. 2015, at 16:21, Tim Graham 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

Re: Make template caching a feature of the Django template engine

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

Re: Make template caching a feature of the Django template engine

c Tamlyn wrote: >>> >>> So. If I understand correctly, this would deprecate the existing cached >>> template loader, replace it with a more powerful, debug ready version (on >>> by default?). Assuming this is what you mean, I wholeheartedly support >>>

Re: Make template caching a feature of the Django template engine

wholeheartedly support this. > There's no reason not to be performant by default. > > Marc > > On 23 Nov 2015 2:16 pm, "Jaap Roes" <jr...@leukeleu.nl <>> wrote: > It’s considered a good practice to enable template caching in Django. It > saves on the overhea

Re: Make template caching a feature of the Django template engine

be performant by default. >> >> Marc >> On 23 Nov 2015 2:16 pm, "Jaap Roes" <jr...@leukeleu.nl> wrote: >> >>> It’s considered a good practice to enable template caching in Django. It >>> saves on the overhead of loading and parsing templates and tur

Re: Make template caching a feature of the Django template engine

mant by default. > > Marc > On 23 Nov 2015 2:16 pm, "Jaap Roes" <jr...@leukeleu.nl > > wrote: > >> It’s considered a good practice to enable template caching in Django. It >> saves on the overhead of loading and parsing templates and turning them >> int

Re: Make template caching a feature of the Django template engine

:16 pm, "Jaap Roes" <jr...@leukeleu.nl> wrote: > It’s considered a good practice to enable template caching in Django. It > saves on the overhead of loading and parsing templates and turning them > into template objects, which can give a nice performance boost when > r

Make template caching a feature of the Django template engine

It’s considered a good practice to enable template caching in Django. It saves on the overhead of loading and parsing templates and turning them into template objects, which can give a nice performance boost when repeatedly rendering the same templates. Currently it’s possible to enable

template-caching: fragment name as variable

before adding a new ticket I just wanted to discuss this issue: when using template-caching it´s sometimes useful to have a variable for the "fragement name". e.g., I want to prefix all caching-variables with "myapp_userid", because I need to delete alle user-related cachi

Re: Template Caching - Ticket #6262

K, I just uploaded another patch to ticket #6262. Comments inline. On Mon, Nov 16, 2009 at 5:58 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Thu, Nov 12, 2009 at 9:15 AM, Mike Malone <mjmal...@gmail.com> wrote: >> Sup, >> >> I've been working

Re: Template Caching - Ticket #6262

:15 AM, Mike Malone <mjmal...@gmail.com> >>> wrote: >>>> Sup, >>>> >>>> I've been working on template caching (ticket #6262) with a mister >>>> Alex Gaynor. The patch is getting pretty stable and I think it's >>>>

Re: Template Caching - Ticket #6262

On Mon, Nov 16, 2009 at 10:04 PM, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Mon, Nov 16, 2009 at 8:58 AM, Russell Keith-Magee > <freakboy3...@gmail.com> wrote: >> On Thu, Nov 12, 2009 at 9:15 AM, Mike Malone <mjmal...@gmail.com> wrote: >>> Sup, >&g

Re: Template Caching - Ticket #6262

On Mon, Nov 16, 2009 at 8:58 AM, Russell Keith-Magee <freakboy3...@gmail.com> wrote: > On Thu, Nov 12, 2009 at 9:15 AM, Mike Malone <mjmal...@gmail.com> wrote: >> Sup, >> >> I've been working on template caching (ticket #6262) with a mister >> Alex Gaynor. T

Re: Template Caching - Ticket #6262

On Thu, Nov 12, 2009 at 9:15 AM, Mike Malone <mjmal...@gmail.com> wrote: > Sup, > > I've been working on template caching (ticket #6262) with a mister > Alex Gaynor. The patch is getting pretty stable and I think it's close > to merge-able, so if anyone wants to take a l

Re: Template Caching - Ticket #6262

On Thu, Nov 12, 2009 at 9:15 AM, Mike Malone <mjmal...@gmail.com> wrote: > Sup, > > I've been working on template caching (ticket #6262) with a mister > Alex Gaynor. The patch is getting pretty stable and I think it's close > to merge-able, so if anyone wants to take a l

Re: Template Caching - Ticket #6262

On Wed, Nov 11, 2009 at 8:15 PM, Mike Malone <mjmal...@gmail.com> wrote: > Sup, > > I've been working on template caching (ticket #6262) with a mister > Alex Gaynor. The patch is getting pretty stable and I think it's close > to merge-able, so if anyone wants to take a l

Template Caching - Ticket #6262

Sup, I've been working on template caching (ticket #6262) with a mister Alex Gaynor. The patch is getting pretty stable and I think it's close to merge-able, so if anyone wants to take a look at what we've got and provide feedback: go! Interesting background reading for people who haven't been

Re: Template Caching

books. So figuring out *some* way of at the > very least easing that transition would help the pill go down quite a > bit. Yes, I agree that accommodating legacy tags is very important. Leaving caching off by default should make things easier on people -- they can choose to upgrade their exist

Re: Template Caching

On Thu, Aug 6, 2009 at 8:15 AM, Jacob Kaplan-Moss wrote: > > Hi Mike -- > > Ah, it looks like my strategy of "wait for someone else to reply and > hope that he sums up my feelings so that I don't have to bother" has > worked perfectly. Thanks, Russ! > > [IOW: I agree

Re: Template Caching

I won't speak to most of this, since Russ and Jacob have said it all, but I do want to respond to one point. On Thu, Aug 6, 2009 at 3:55 AM, Russell Keith-Magee wrote: >> By simply checking that the template has a ``render`` method in >> ``get_template``, we get the added

Re: Template Caching

Hi Mike -- Ah, it looks like my strategy of "wait for someone else to reply and hope that he sums up my feelings so that I don't have to bother" has worked perfectly. Thanks, Russ! [IOW: I agree completely with Russ.] I'll be digging into this patch in some detail, but based on what I've seen

Re: Template Caching

r enough along that I have a working > implementation, so I thought I'd share here and see if anyone had any > thoughts / comments. I've attached my diff to ticket #6262, so > visit http://code.djangoproject.com/ticket/6262 to check it out. > > I'd like to add template caching as a f

Template Caching

any thoughts / comments. I've attached my diff to ticket #6262, so visit http://code.djangoproject.com/ticket/6262 to check it out. I'd like to add template caching as a feature to Django 1.2, and am willing to do whatever is necessary to make this happen. If you'd rather read prose, here's