On Tue, 2008-11-25 at 00:28 -0800, Ulf Kronman wrote: [...] > The peculiar thing is that this problem appeared suddenly on monday > morning, with no apparent reason, more than updating to latest version > of Django from the CVS. (I may also have tampered with some code last > weekend, but forgotten. Did some experiments with comma-formatted > float output to MS Excel, but have commented away that code as far as > I can see.)
Nothing has changed in Django in the past few months (or years) that would affect this, as far as I can see. [...] > > Django doesn't call setlocale() itself and it would be a little tricky > > to do so (it affects the locale for all threads in that process, which > > could well lead to interesting behaviour on a multipthreaded Apache > > setup, for example). > > OK, but would that effect the Django template engine? I don't understand the question. All I'm saying is that Django doesn't call setlocale(), so it's quite believable that if your system is set up to process things in the Swedish locale by default, that is what will be happening. 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 [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-users?hl=en -~----------~----~----~----~------~----~------~--~---
