Hi again, > Nothing has changed in Django in the past few months (or years) that > would affect this, as far as I can see.
OK, so the reason must be me doing some changes (which I have forgotten) to the code. > > > 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(), You also said that you could see some interesting behaviour on Apache, and my (maybe stupid) question was meant to be if that somehow could affect the Django template engine. > 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. I tried to change my OS settings to use point as decimal delimiter, but it didn't help, so I presume that there is something else than the OS settings that is telling floatformat to expect comma as decimal delimiter. Regards, Ulf --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---