On Wed, 2009-01-28 at 22:50 -0500, Karen Tracey wrote: > On Wed, Jan 28, 2009 at 9:51 PM, Todd O'Bryan <toddobr...@gmail.com> > wrote: > > On Sun, Jan 25, 2009 at 7:13 PM, Karen Tracey > <kmtra...@gmail.com> wrote: > > Sounds related to: > > > > http://code.djangoproject.com/ticket/8193 > > > > Karen > > > > > That's exactly what it is, and that hasn't been fixed because > people > don't think it's really a bug. > > No, I don't think that's an accurate representation of the status. > The triage state is Accepted and furthermore Malcolm even assigned it > to himself, meaning he's intending to fix it. Per this comment: > > http://code.djangoproject.com/ticket/8193#comment:20 > > working on the fix has revealed other problems so it is not as simple > as one might hope. So it's in the queue to be fixed, probably (I'm > just guessing) prioritized behind some 1.1 feature work.
That's correct. Also, this particular thread has provided the first example of standard behaviour causing a problem, which is something that's been requested a few times in that ticket and related threads. It will be fixed for 1.1. Since we now have a case of normal Python usage triggering a problem, it will also be back-ported to the 1.0 branch. All in good time. For now, not using "from __future__ ..." is an acceptable workaround. Live in the present, not the future for a little while. :-) Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
