Re: Django 1.0.2 Thread safety
>I've hit http://code.djangoproject.com/ticket/10470 on production what's the the symptom when you hit this bug? P.S. I'm wanting to use mod_wsgi in daemon mode with threading to conserve memory. I guess I'll manually update or wait for v1.1 --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django 1.0.2 Thread safety
On Wed, Jul 1, 2009 at 9:38 AM, Miles wrote: > > On Jun 30, 8:10 am, Thomas Guettler wrote: > > Hi, > > > > I hit this bug some time ago, too. If you run SVN 1.0.X you get the > > bug fixes for free. > > > > Thomas > > Yeah, but then you have to test your releases really carefully on each > svn up - not every commit has gone through a complete test run, as > 10036 shows, up to 10039, those Django versions won't even start. > That's pretty rare, and such problems are usually noted and fixed pretty quickly. Here it looks like it took about half an hour. > > Slightly off topic: when is 1.0.3 scheduled for? There have been quite > a few commits in the 1.0.x branch since 1.0.2, bugfixes only, if there > aren't any problems it would be nice to have a tested release to > upgrade to. > About the same time as 1.1. Karen --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django 1.0.2 Thread safety
On Jun 30, 8:10 am, Thomas Guettler wrote: > Hi, > > I hit this bug some time ago, too. If you run SVN 1.0.X you get the > bug fixes for free. > > Thomas Yeah, but then you have to test your releases really carefully on each svn up - not every commit has gone through a complete test run, as 10036 shows, up to 10039, those Django versions won't even start. Slightly off topic: when is 1.0.3 scheduled for? There have been quite a few commits in the 1.0.x branch since 1.0.2, bugfixes only, if there aren't any problems it would be nice to have a tested release to upgrade to. Miles --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: Django 1.0.2 Thread safety
Hi, I hit this bug some time ago, too. If you run SVN 1.0.X you get the bug fixes for free. Thomas Miles schrieb: > There should be a little warning in the 1.0.2 docs or on > http://code.djangoproject.com/wiki/DjangoSpecifications/Core/Threading > that it is *not* thread safe. > > I've hit http://code.djangoproject.com/ticket/10470 on production, > applied the patches manually. Please make sure you apply both > http://code.djangoproject.com/changeset/10036 and > http://code.djangoproject.com/changeset/10040, the first one contains > a bug which will deadlock the server. -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
