On 8/11/06, James Bennett <[EMAIL PROTECTED]> wrote: <snip> > 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 result of a non-existent > 'templatetags' module. > > This is both frustrating and counterintuitive.
I agree. Similar ignoring of ImportErrors in core/management.py has caused me many hours of unproductive head-slapping. > > There are two ways I can think of to solve this problem: <snip> > 2) Tweak django/templatetags/__init__.py to introspect the ImportError > it gets and figure out whether the exception came from a non-existent > 'templatetags' module (in which case it can be safely quashed) <snip> > Obviously I prefer the latter, since it results in more intuitive > behavior, but I'm interested in hearing what other people think about > this. I agree. Django should not be asking it's users to write boiler-plate code, even if that boiler-plate may be found somewhere 'obvious' in the documentation. a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
