At the end of the angsty autoescaping thread (said angst in no small part from my direction ^_^), I floated the idea that perhaps my concern over autoescaping was pointed in the wrong direction -- that it might be time to split Django's template module out into a standalone library. The idea has been raised before, but discussion always hits the point of "good idea, but a PITA ..." and a combination of time constraints and the bystander effect kick in to shelve it.
Since I've been championing the use of Django's template library as a general purpose library, and spending plenty of time in the guts of the template code while writing the taghelpers module, I may as well step up and offer to do this. And no, I don't want another Jinja [1] [2]; I want a Django template library that's still distributed as part of Django, in the Django namespace, and available in its separate split-off form from the Django website, similar to how the various Twisted modules are distributed [3]. I know there are various obstacles here, the largest one being the use of Django settings in the template code -- but nothing looks unsurmountable. I'd ideally like to have this done in time for Django 1.0, and to ensure stable releases in line with future Django releases. So ... thoughts? [1] http://jinja.pocoo.org/ [2] Not to disparage Jinja; I just have a different goal in mind. [3] http://twistedmatrix.com/trac/wiki/TwistedProjects --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
