It retries loading the template with each template loader to figure out
which paths were tried. Since the multiple templates engines refactor,
this still works, but only if there's only one Django templates engine
configured.
This logic should be embedded in the template engine. Third-part engines
should have access to similar functionality through a public API.
Some ideas were brought up in [https://groups.google.com/d/msg/django-
developers/VFBLAoPSplI/H_hQq29u8PcJ this django-developers discussion].
--
Ticket URL: <https://code.djangoproject.com/ticket/24120>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/24120#comment:1>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/24120#comment:2>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"adff499e47d99f6b40307acc1ace95508e3c5910" adff499]:
{{{
#!CommitTicketReference repository=""
revision="adff499e47d99f6b40307acc1ace95508e3c5910"
Fixed #24119, #24120 -- Formalized debug integration for template
backends.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24120#comment:3>