I knew I couldn't be that easy. Thanks for the heads up. Any other work around? besides the patch mentioned.
On Apr 15, 11:17 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Thu, Apr 16, 2009 at 12:15 AM, Sean Brant <brant.s...@gmail.com> wrote: > > > If you set request.urlconf in say a Middleware then the reverse > > function and the url tag will not work because those try to match > > based on your ROOT_URLCONF. I was trying to find a solution to this > > problem and came across this ticket. > >http://code.djangoproject.com/ticket/5034 > > > Then It dawned on me what if I also override settings.ROOT_URLCONF in > > my middleware when I am setting request.urlconf. This seemed to solve > > my problems. > > > I now wonder If what I did is a good and solid idea. If anyone out > > there has come across this let me know. It seems to work fine for now > > though. > > It's a bad idea because your application is not threadsafe at all, if you > try to run your application in a threaded enviroment you will get lots of > reverses that return incorrect data since the settings are shared state. > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
