On 4/26/06, James Bennett <[EMAIL PROTECTED]> wrote:
> But it's still magic, and it means that any given tag library can be
> imported from either of two locations -- its actual conventional
> Python path, and its "magic" location in 'django.templatetags'.
>
> So... should this bit of magic stay, or should it go?
This bit of magic doesn't bother me much, because it isn't really
exposed to programmers (as you noted), but I'd be happy to consider
other solutions. One solution that absolutely *wouldn't* work, though,
is iterating over INSTALLED_APPS each time {% load %} is called.
Fun fact: The django.templatetags technique of appending to __path__
is the same way django.models worked in pre-magic-removal Django.
Adrian
--
Adrian Holovaty
holovaty.com | djangoproject.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
