Overriding Variables of Outer Scopes about jinja HOT 14 CLOSED

I will keep it in mind for the new compiler backend, but in the current one that is not possible to achieve for performance reasons.

from jinja.

I'd like to see this too.

from jinja.

+1

from jinja.

I would like to see this too.

I'm trying to perform simple running totals in some generated data..and that functionality is what I need.

from jinja.

+1

from jinja.

+1

from jinja.

+1

I also think that this behaviour should be unacceptable:

{% set first_run = True %} {% for i in range(3) %}
{% for j in range(3) %} {% if first_run %} {% set first_run = False %}
• {{ i }}, {{ j }}
{% endif %} {% endfor %}
{% endfor %}

This will output 3

from jinja.

+1

I also think that this behaviour should be unacceptable:

<ul>
  {% set first_run = True %}
  {% for i in range(3) %}
  <ul>
    {% for j in range(3) %}
    {% if first_run %}
    {% set first_run = False %}
    <li>{{ i }}, {{ j }}</li>
    {% endif %}
    {% endfor %}
  </ul>
  {% endfor %}
</ul>

This will output 3 <li> tags, but it should output only one.

The variable resets after each outer loop run, even though it was declared OUTSIDE of all loops.
I can't see how this would be expected behaviour. Is this a bug ?

from jinja.

+1

from jinja.

This would very useful when templating JSON files. +1

from jinja.

+1

from jinja.

Me too, could really use an override and it'd be great if the template designer docs explicitly mentioned this behavior!

I had to work with some data in an (admittedly horrible) format and was puzzled at why the followed pre-pass didn't work...

{% set last_one = none %}
{% for row in rows %}
    {% set last_one = row.field %}
{% endfor %}

I agree with @ruiposse's comment that having a variable first set outside all loops reset itself inside them is very unexpected.

from jinja.

+1

from jinja.

I'm going to close this. This cannot work in all cases in Jinja2 and I do not really wish on supporting it.

from jinja.