On Monday 09 December 2013 14:58:34 unai wrote: > > > 2. This solution will complicate the template development. e.g. if a > > > > application overwrite the "admin/change_form.html" template and a > > developer wants to update this template, he will have to search this > > template in every app. He does not know what application is > > overwriting this template... With the current solution [1] if you > > overwrite the "admin/change_form.html" template this only (the most > > common usecase) will be in a place, this will be in the template > > project directory. > > If I understand you correctly, you are saying that if an app extends an > other app's template and the users want to extend this very same template, > they don't know what app they are extending. > I read Pablo's concern as: If the skipping is done in each loader, does "recursive" self-reference work across loaders?
If not, then you cannot use the feature from project templates to extend app- provided templates -- you must do so in an app, and then the question of which app and app order becomes important. Shai. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/2734728.tmOATH7Xvm%40deblack. For more options, visit https://groups.google.com/groups/opt_out.
