Per discussion with Aymeric, it sounds like the least ambiguous behavior
it to raise an exception if an included or extended template has a
different engine than that of the current template.
This affects the IncludeNode, ExtendsNode, and InclusionNode.
--
Ticket URL: <https://code.djangoproject.com/ticket/24577>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/24577#comment:1>
* owner: nobody => sgzsh269
* status: new => assigned
--
Ticket URL: <https://code.djangoproject.com/ticket/24577#comment:2>
* owner: sgzsh269 =>
* status: assigned => new
--
Ticket URL: <https://code.djangoproject.com/ticket/24577#comment:3>
* cc: desecho@… (added)
Comment:
I can't reproduce this issue. Can you offer a sample project?
--
Ticket URL: <https://code.djangoproject.com/ticket/24577#comment:2>
Comment (by Tim Graham):
A start at solving this for `{% Include %}` is available as the second
commit of the [https://github.com/django/django/pull/7960 PR] for #27722.
--
Ticket URL: <https://code.djangoproject.com/ticket/24577#comment:3>
* Attachment "24577.diff" added.