Re: Custom filters failing with "no module"
James Bennett
> No matter what I try, I get:
>
> django.template.TemplateSyntaxError: 'javadoc_filter' is not a valid tag
> library: Could not load template library from
> django.templatetags.javadoc_filter, No module named javadoc_filter
Cross-replying here because it's worth discussing...
I asked a while back if the current tag-loading mechanism was a bit
too "magical", and the general consensus (including my own opinion)
was that it wasn't because end users typically never see the guts of
tag loading.
But I keep forgetting that we display the above message on an
InvalidTemplateLibrary exception, and I was wondering how folks would
feel about changing it to something a bit more helpful that doesn't
include the confusing "django.templatetags" path... maybe something
like "The tag library '%s' either could not be imported or contained
errors" ?
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
Malcolm Tredinnick
I have a hunch there is a ticket open for this. Or maybe it got canned.
I remember reading it and thinking it wasn't insane (very few tickets
are insane, so this didn't stand out merely on those grounds).
It's something that would be nice to have (i.e. an accurate traceback),
but not something I'm likely to drop what I'm doing at any point to
implement. Long way of saying, I'm not against the idea of improving it,
but unless I'm on a long plane flight or something, I'm unlikely to do
so in the foreseeable future.
Regards,
Malcolm