The current implementation of the filesystem loader (looking at
`self.engine.dirs`) evolved naturally from its origins looking directly at
`settings.TEMPLATE_DIRS`, but a more flexible implementation would just
take `dirs` as an extra loader parameter (we have precedent for loaders
that take additional args: the cached loader). That allows inserting
potentially two instances of the filesystem loader into the loaders chain,
looking at two different lists of dirs, without needing a subclass.
--
Ticket URL: <https://code.djangoproject.com/ticket/27598>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/7685 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27598#comment:1>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"92c5eeac3358e8243e29604d51b724f46fd5305f" 92c5eeac]:
{{{
#!CommitTicketReference repository=""
revision="92c5eeac3358e8243e29604d51b724f46fd5305f"
Fixed #27598 -- Allowed specifying directories for a filesystem template
loader.
Thanks Carl Meyer for review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27598#comment:2>