>a simple solution would be to use lazy loading of the settings >module in django.template, change all template code to access >the settings via django.template.settings, and let an external >user configure the template package *before* loading the first >template:
Should be doable since now settings are stored in an object and not a module - and actually this would be nice to have for other situations, too. I think about the Pasteification, it might benefit from this, too - since this config setup could just happen in the thread as the first thing in handling a request, so that switching settings becomes even easier. bye, Georg
