On Wed, Mar 17, 2010 at 4:53 AM, Sean Brant <brant.s...@gmail.com> wrote: > A co-worker of mine noticed this bug today > http://code.djangoproject.com/ticket/13125. > Should it be marked for 1.2 or punt it until after the release > candidate? It looks to be a bug so it could probably go in at anytime. > Let me know your thoughts.
I've just marked the ticket accepted. It isn't 1.2 critical, since the currently behavior has existed since pretty much the beginning of time, but it does strike me as an edge case that is worth catching. The patch also requires some minor tweaks before it is trunk-ready; comments on the patch. 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 django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
