On Sat, 2007-06-30 at 07:29 -0500, Jeremy Dunck wrote: > On 6/30/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > ... > > No, this isn't possible. The settings file is read once and then the > > settings are cached (and are assumed to be static). > > Actually, it *is* possible to alter the urlconf that's processed on a > per-request basis, though TEMPLATE_DIRS is static. > > The URLConf can be overridden by adding an "urlconf" attribute to the > request object via a request middleware. > http://www.djangoproject.com/documentation/middleware/#process-request > > The request.urlconf attribute should be in the same format as the > settings.ROOT_URLCONF, which is to say, a string of an importable > module with an urlpatterns attribute (and friends).
Oh, yeah. I'd forgotten about that feature. There's an example of it's use over at the Fredrik Lundh's site: http://effbot.org/zone/django-multihost.htm (you don't need the patch to core/handlers/base.py any longer, since that's now in the main code). Note, however, that reverse URL resolving does not yet work. That's ticket #3530 and one day I'll get around to checking it in. Regards, Malcolm > > > -- Everything is _not_ based on faith... take my word for it. 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 -~----------~----~----~----~------~----~------~--~---
