On 07-Jul-06, at 5:35 PM, Malcolm Tredinnick wrote:
> In django/templatetags/__init__.py, try putting in some printing there > (what does __path__ end up looking like, for example). Maybe in the > ImportError exception block, catch the exception and print it out > to see > if you are raising some import error (although from what you are > saying, > that shouldn't be happening). solved. django *was* looking in the correct place, but the templatetag had an error in it (python2.4 decorator in a 2.3 install), but instead of saying 'app.templatetags.tag.py import error' it was saying 'django.templatetags.tag.py import error'. This hardcoded error message led me to think that django was looking in the wrong place -- regards kg http://lawgon.livejournal.com http://avsap.org.in --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
