I've created a ticket for this task:
http://code.djangoproject.com/ticket/1321
On Feb 3, 2006, at 3:28 AM, [EMAIL PROTECTED] wrote:
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 th
>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 sett
Adrian wrote:
> Anybody care to tackle the separation of Django templates? The main
> thing is decoupling it from django.core.settings (and, hence,
> DJANGO_SETTINGS_MODULE), of which I'm not sure what the best
> approach would be.
a simple solution would be to use lazy loading of the settings
m
Yes, sort of. TurboGears is using what they're calling the "open
template plug-in engine" something or rather. The underlying effect is
it provides a unified way to render templates. It's still undergoing
some fine-tuning, and is not part of TurboGears itself. Here's the
'spec' for making a templa
On 01/31/06 22:25, Ian Holsman wrote:
are you proposing a standard interface to templating languages in python
ala WSGI but for templates?
There's currently a discussion about just that on the python web-sig
mailing list.
http://mail.python.org/pipermail/web-sig/2006-January/thread.html#1
are you proposing a standard interface to templating languages in python
ala WSGI but for templates?
On 2/1/06, Ben Bangert <[EMAIL PROTECTED]> wrote:
>
> Adrian Holovaty wrote:
> > Anybody care to tackle the separation of Django templates? The main
> > thing is decoupling it from django.core.se
Hehe. A month ago I tried to use the django template for my pocoo
project but it ended up in rewriting the template engine. Not because
it was impossible to strip it out. (It worked quite well) but for pocoo
I wanted a better syntax for the filters.
But personally I find the idea of spliting them
jfyi,
GvR wrote also:
>> Regarding a standard, there is sort of a standard
>> developing, that TurboGears has pioneered, and Pylons also
>> supports. It's called template plug-ins:
>> http://www.turbogears.com/docs/plugins/template.html
>
> Thanks for the pointer! Perhaps it is right -- if other fr
Adrian Holovaty wrote:
> Anybody care to tackle the separation of Django templates? The main
> thing is decoupling it from django.core.settings (and, hence,
> DJANGO_SETTINGS_MODULE), of which I'm not sure what the best approach
> would be. Note that in the magic-removal branch, the template syste
On 1/31/06, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Won't it be cool if django splits the tree into different reusable packages,
> developed and maintained by you folks only. One can say there are almost
> independent, but it requires lots of familiarity in django to understand
> this, an outsi
Hi all,One of the first thought that came to my mind when I read django documentation is, Django is really a set of related projects, Django ORM, Django Templates and Django Webframework, and can be used independently of each other. Came across this post by Guido:
http://www.artima.com/weblogs/vie
12 matches
Mail list logo
