#1586: [patch] cooler version of django.template.loaders.app_directories
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Type: enhancement | Status: reopened
Priority: normal | Milestone:
Component: Template system | Version: magic-removal
Severity: minor | Resolution:
Keywords: template loader |
-----------------------------+----------------------------------------------
Changes (by [EMAIL PROTECTED]):
* resolution: wontfix =>
* status: closed => reopened
Comment:
I only reopened to get your attention, feel free to close if you're still
against it ... that'll be that then.
I wouldn't mind if you said that you simply weren't interested and there
are more pressing things on your mind.
Though, I'm confused about what you wrote. How does this make "finding
templates confusing"? You know which app it is from, voila, there it is.
The original loader makes it much harder to find the actual place of a
template.
You can still overwrite templates if you must--in the example above, you
could use the directory based template loader, set up directories
'/templates/app1/index' or so, and if you put the directory based loader
first, it will find the overwriting template first.
Note that I don't want to replace the original loader--this is an
addition. Isn't 'contrib' the place for such user contributed stuff that
doesn't really belong into the core?
--
Ticket URL: <http://code.djangoproject.com/ticket/1586>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@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-updates
-~----------~----~----~----~------~----~------~--~---
