On Dec 7, 6:35 pm, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> On Dec 7, 2007 12:56 PM, Vinay Sajip <[EMAIL PROTECTED]> wrote:
>
> > this be allowed/disallowed/checked for? As for standard template
> > loading, there's no reason that the standard template loading
> > (app_loader) code could not be modified to work with App instances,
> > using whatever logic to use the application path and/or label to
> > locate the templates. Or have I misunderstood Malcolm's comment?
>
> The problem here is that a distributed app has to expect specific
> paths to its templates, both for its views (for render_to_response,
> for instance) and its templates (for extends and include). If my
> template says "{% extend 'modular/module.html %}', what would happen
> if someone had "App('modular', name='mod_app')"? How would the extends
> tag be able to locate the correct template if someone essentially
> renamed the app?
>
The current code in django/template/loaders/app_directories.py appears
to search in the directory 'templates' relative to the directory
containing the app module. I can't quite see why this needs to change:
it's independent of the app label, shouldn't that be OK?
Regards,
Vinay Sajip
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
