{% include "tpl" with foo=x bar=y %}

[Johannes Dollinger]

This is a simple but useful syntax extension. The separator could also be "and": {% with foo as x and bar as y %}.

{% include "tpl" with foo as x %} would be equivalent to {% with foo as x %}{% include "tpl"%}{% endwith %}, which is more transparent that a trivial inclusion_tag.

Use a common parser for include, with and possibly blocktrans.

[Johannes Dollinger]

#9456 has a patch for {% with foo as x and bar as y ... %}.

[(none)]

Milestone post-1.0 deleted

[Antti Kaihola]

[patch] Allows multiple bindings in the {% with %} tag. Python <=2.4 compatible with tests and documentation.

[Antti Kaihola]

I took eibaan's patch​ from #9456 (which is marked as a duplicate of this ticket) and made the following improvements:

• added Python 2.3 and 2.4 compatibility by not using 2.5's any() built-in function
• now raises an error if something else than "and" is used as a delimiter
• added documentation
• added three more tests

The patch is based on r10188.

[Antti Kaihola]

To clarify, the patch above does not implement the {% include "tpl" with foo as x and bar as y %} syntax. It only extends the {% with %} tag in a backwards-compatible way. I also chose "and" as the delimiter since I felt it fits existing syntax better than a comma.

If core devs decide the suggested {% include %} syntax is a good idea, I'm willing to extend the patch.

[Łukasz Rekucki]

Improved patch against r13716.

[Łukasz Rekucki]

Attached patch extends both "with" and "include" tags with following syntax:

{% with foo as x and bar as y %}
{% include "partial.html" with label="Hello world" foo=baz %}

After some thought I decided to use keyword style arguments in include. Other tags use "as" to introduce new variables to the current scope. Using it here could give a false impression that the template is actually rendered to a variable (like the url tag).

[Chris Beaven]

There are two separate feature requests here, one for {% with %} and one for {% include %}.

Although similar, they are separate requests which may have separate resolutions. Let's use this one for {% include %} - I'm reopening #9456 to track {% with %}.
I'm more keen on this one, ambivalent about the other one.

[Łukasz Rekucki]

Patch without "with" related stuff. Added docs and one more test.

[Chris Beaven]

My latest changes can be found here: ​http://github.com/SmileyChris/django/compare/master...7817-include-with

[Jannis Leidel]

Something like this seems more reasonable to me: {{{
{% include "name_snippet.html" with "Joe" as name and "Hello" as greeting %}
}}}

[Russell Keith-Magee]

Following a ​BDFL pronouncement, this has been accepted, using the {% include "templ.html" with foo=x bar=y %} syntax. Related ticket: #9456.

[Chris Beaven]

(In [14922]) Fixes #7817 and #9456.

• The include tag now has a 'with' option to include to provide extra context vairables to the included template.

• The include tag now has an 'only' option to exclude the current context when rendering the included template.

• The with tag now accepts multiple variable assignments.

• The with, include and blocktrans tags now use a new keyword argument format for variable assignments (e.g. {% with foo=1 bar=2 %}).

[Jacob]

Milestone 1.3 deleted