Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Fixing app_label
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Marty Alchin  
View profile  
 More options Dec 7 2007, 1:35 pm
From: "Marty Alchin" <gulop...@gamemusic.org>
Date: Fri, 7 Dec 2007 13:35:42 -0500
Local: Fri, Dec 7 2007 1:35 pm
Subject: Re: Fixing app_label
On Dec 7, 2007 12:56 PM, Vinay Sajip <vinay_sa...@yahoo.co.uk> 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?

-Gul


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.