On Sat, Apr 3, 2010 at 9:58 PM, Dennis Kaarsemaker <[email protected]> wrote: > On ma, 2010-03-22 at 08:53 -0400, Karen Tracey wrote: >> On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso >> <[email protected]> wrote: >> Marcob wrote: >> > Please, does anybody know which patch I need to apply to >> 1.1.1 to fix >> > this strange problem? >> >> http://code.djangoproject.com/changeset/12807 ? >> >> >> No, turns out it was a change made farther back, and it was in fact a >> change specifically in response to the change in Python: >> >> http://code.djangoproject.com/changeset/11821 > > When can we expect to see this patch in a 1.1.x release? The problem is > coming up in #django suspiciously often (3 times in the last week so > far).
The code is in the 1.1.X branch, which means it will be included in the next 1.1 release. At this point, the date for that release is tied to the release of Django 1.2. The current schedule estimates that should be around April 26, but that's entirely dependent on the rate at which the final 1.2 blocking bugs are cleared out. Yours, Russ Magee %-) -- 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.
