On Sun, 2007-11-11 at 20:22 +0100, [EMAIL PROTECTED] wrote: > Hi, > > the include method used in urls.py is very nice. Nevertheless I > miss something: It would be nice if you could use some settings, > which only get used, if the request follows this include. > > It would be good, if you could activate some middleware and alter > the TEMPLATE_DIR only, if the url starts with e.g. '/myapp/...'. > > This would make django more flexible. The chance that template names > clash could be reduced very much. > > Maybe this is already possible, and I have not seen it.
This is a lot harder than it sounds to get right. Your settings file controls a number of things that are imported into your global process space, for example, so as soon as you allow stuff like this, the potential (and practical likelihood) of inadvertent collision arises. We're (well, I'm) doing some design on this for allowing multiple Django projects to run under a single interpreter, but it is fiddly. I doubt I'd be particularly interested in extending it to per-app or anything like that, since it's too error-prone. It might also be possible one day to have Django's URL configuration delegate to another WSGI application if a particular pattern is matched, which would allow you to embed entire other collections of Django projects that way. However, that's probably a ways off yet (it's a nice idea and I know somebody who's written a prototype, but I'm not going to uncloak them here. So it's possible). Template name collisions can be avoided either by using the app_name/templates/app/<template_name> style of naming if you're using the app_loader, or possibly better, picking likely-to-be-unique names initially (such as app-<template_name>.html) and then only using the file-based template loader. At this level, it's exactly the same as not having Python modules with the same name: it would be nice if it was always possible to avoid collisions and ambiguity, but that's not possible, so the developer has to take preventative measures, such as not picking really common names for their templates. Regards, Malcolm -- If it walks out of your refrigerator, LET IT GO!! http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
