Question

I have written a custom template loader, and templates may change during the lifetime of a server. As I understand it, the first time a template is loaded it is parsed into the in-memory node-tree and thereafter it is cached.

Is it possible to invalidate this caching by issuing a command to say ‘unload this template so it is re-loaded next time’? Or can my template loader take care of this?

Answer 1

This:

the first time a template is loaded it is parsed into the in-memory node-tree and thereafter it is cached

is not true. Templates are only cached if loaders is not specified and the key TEMPLATES -> OPTIONS['debug'] is True. The documentation says:

class cached.Loader

This loader is automatically enabled if OPTIONS[‘loaders’] isn’t specified and OPTIONS[‘debug’] is False (the latter option defaults to the value of DEBUG).

So, in answer to your question, if you’re using a custom loader, templates are not cached by default.