On 8/12/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> Yeah, I agree that we should improve the templatetag loading magic.
> What about doing *both* -- improving the docs to note the ImportError
> gotcha, *and* introspecting the ImportError?
Sounds good, though if we introspect the ImportError
On 8/10/06, James Bennett <[EMAIL PROTECTED]> wrote:
> 1) Document the way templatetag loading works, and advise tag authors
> to wrap any imports they need in try/except and handle the situation
> as appropriate (for example, by returning nothing from their tag, or
> possibly raising ImproperlyCo
This is another case* where using something like setuptools entry
points for loading 3rd-party plugins would make all of these problems
go away. Entry points specifically would impose an additional burder on
app writers, though, because they'd have to register their tag
libraries explicitly in set
On 8/11/06, James Bennett <[EMAIL PROTECTED]> wrote:
> The reason for this is that django/templatetags/__init__.py, when it
> loops over INSTALLED_APPS to find templatetag libraries,
> indiscriminately quashes ImportError -- apparently on the assumption
> that any ImportError being raised is a r
This is a bit long for a ticket writeup, but I wanted to get some
comments on it, so here goes:
The "magic" that still goes on in the templatetag system has been
discussed before on the list[1], and the consensus was that, since
it's relatively invisible and harmless, it's OK for it to stay.
Exc
