On 2/21/08, Vasily Sulatskov <[EMAIL PROTECTED]> wrote: > I am thinking about integrating get_template_from_string() > functionality into Template Loaders classes. I think it will have > numerous benefits (like possible caching for people who really need > it, and many other uses).
The idea seems reasonable to me -- get_template_from_string() is a bit silly, isn't it? The downside is that such a change would break any existing custom template loaders. That's a non-trivial breakage, I think -- I think template loaders are fairly well-used (there's at least a dozen on djangosnippets, for example). So I'll certainly look at your patch, but I'm probably -0 unless you can make it work in a backwards compatible manner. Off the top of my head that doesn't sound too hard: just allow template loaders to return either fully-compiled templates or the template source itself? Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
