On Tue, 2008-10-14 at 08:21 +0100, [EMAIL PROTECTED] wrote: > I did Google around but obviously missed this. Having read it and followed > the links it is definitely the same issue. I will try and investigate but > I think bigger brains than mine have already given up so I may have to > find a dirty work round. Thanks for pointing me in the right direction.
I suspect it's going to turn out to be something simple in the end, but I must admit I haven't had a chance to sit down and look at that ticket. It's sufficiently uncommon that my times been going elsewhere and I've been hoping somebody seeing the problem will be able to make the time and have the motivation to work out the cause. We'll certainly fix it when we get a chance, so don't give up hope or anything, but there have been a few higher-impact bugs around that I know I've been spending my available time on first. 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
