On 6/6/07, Andrew R <[EMAIL PROTECTED]> wrote: > whereas I just want it to import "javadoc_filter" from my current dir. I'm > sure > this is by design in django but there must be a way around it.
This is one of the tricky bits of Django that you don't often see. Django needs to have some consistent way of locating user-supplied tag libraries, so django/templatetags/__init__.py contains a short bit of code which loops through INSTALLED_APPS looking for any applications which include a "templatetags" module, and extends the import path under "django.templatetags" to include those modules. The end result is that your own code, if it knows exactly where your tag library lives, can import from it directly as expected, and Django can also find it automatically because it'll also show up under "django.templatetags". Django accomplishes this by trying to import the "templatetags" module of your application, and traps ImportError on the assumption that it will be raised when there is no such module to import. The problem is that if your custom tag library exists but also contains a bad import of its own, it will raise ImportError and Django will assume that there is no tag library to be loaded there; you'll end up seeing the "Could not load template library" message. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
