On Jun 14, 5:23 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Thu, 2007-06-14 at 03:40 +0000, Graham Dumpleton wrote: > > [...] > > > No one > > though seems to want to update the documentation. > > Which ticket is this? > > You keep complaining about this and yet it's unlikely that somebody like > me is going to remember a throwaway comment on the list when I sit down > to do some work, given how unlikely I am to stumble across the problem > myself. Sometimes I remember to capture your comments in ticket reports > but usually not because there's a lot of mail to plough through and > answer each day. You keep referring to "ancient" versions, but a > maintainer's idea of ancient is often more aggressive than the > real-worlds. So we would want to include the version at which this > became a safe thing to do. > > Please help us to make your life easier.
I have occasionally pointed it out that I believe it is possibly wrong, but no one yet that I am aware of who is connected with Django development has acknowledged that this may be the case even though in the past I have asked for someone who knows better to comment. I don't personally use Django for anything nor know the code in any detail so I can't back up my observations with any proof and have been waiting for anyone connected with actual Django development to acknowledge that my comments may be true to any degree and start an informed conversation about it. Since there has been silence I have only been able to take it that people either don't really care or disagree and that prefork is seen as the only safe way to use Django. I haven't created a ticket as I saw the mailing list as a preferred place for initial discussion especially when I have seen tickets where comments were added taking issue with people using it for conversations. So, if I knew for sure if my complaint was even half valid I would create a ticket, but I don't know as no one with any authority has responded. By responding are you acknowledging that Django probably is okay to use with worker MPM or are there still issues with database caching or other areas? BTW, mod_python 3.1.3 was released almost 3 1/2 years ago. Although mod_python 3.1.4 was released 2 1/2 years ago, it only contained a security bug fix with code otherwise exactly the same. Given that there have been two major releases and three minor releases since then those 3.1.X versions are looking quite old. Graham --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
