I would like to bring up the topic discussed both in this ticket: http://code.djangoproject.com/ticket/4438 and here in this group as well: http://groups.google.com/group/django-developers/browse_thread/thread/4125cb192c72ed59/7a9f379f5e5b9090
I also found a snippet which implements something similar, here: http://www.djangosnippets.org/snippets/1099/ Of course, the snippet didn't really work right and had to be beaten into submission to even give the illusion of working. Obviously, as discussed previously, none of these options are optimal. They all have their fair share of issues, and there really should be a better way to go about it. Two of these options were mentioned by Malcolm in the aforementioned thread; thread-local settings, or a more dynamic site object. I found it odd that this discussion fell flat after a very short period, over a year ago. Personally, this was a feature which I initially assumed Django supported, simply because it seemed like such an obvious one to me. Now I find myself struggling to get a project working how I want due to the lack of what, in my mind, should be a readily available feature. Now I know from reading all of the previous discussions that this really isn't such an easy implementation, but given the state of Django today, how much work would really be involved? For that matter, what design direction would be the preferred one? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
