I'm +1 on the optional "with" parameter for {% include %}. -1 on
adding a new tag for this.
I also use {% with %}{% include %} a lot in templates but we should
follow with/blocktrans syntax for consistency:
{% include "part.html" with obj.title|capfirst as title and "large"
as main_class %}
A
jango internals and take out the useful
stuff from pluggable-model-i18n.
Greetings,
--
Gonzalo Saavedra
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send
on__contains='text')
-
both could use the request language wich seems also as a nice default
for templates, queries in vies and for adding translation support to
3rd party apps.
-------
I know this is not the best time
uld include a conf.py file looking like so:
[...]
+1
Good work Shai! This is useful whether it gets into trunk or not, hope
to read some
committer's opinions soon tho :)
--
Gonzalo Saavedra
--~--~-~--~~~---~--~~
You received this message because you are subscribed
