Karen Tracey wrote: > Can't answer as to why it is the way it is, but Gary did open a defect to > track the issue, and it has a patch: > > http://code.djangoproject.com/ticket/6094 > > Someone else a couple of weeks ago opened another couple of defects covering > the same issue, and when pointed to the first defect updated the patch to > apply cleanly against (then-current) trunk. So there's a patch to try and > report results of, if you like. No one has piped up to say why this > shouldn't be changed, so I'd guess it's just waiting on someone with enough > expertise and time to give it some attention.
I was mainly waiting for review and some testing. Malcolm has now reviewed it. I have not tested it in a ModPython setup yet. So please, test and note your results here. I've just added an updated patch to the ticket, enjoy. Gary --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
