On Tue, 2007-06-26 at 15:09 +0200, Jens Diemer wrote: > > Woops... I used apache2 and django via cgi... > > This works fine so far. Until now. > locale.getdefaultlocale() returns (None, None) > Don't know why. A restart of apache doesn't change anything.
That's a recent change to the code (within the last 24 hours). That is something you *really* need to check as one of the first steps when behaviour changes -- if your tests fail today, go back to yesterday's version and try that. If it works there, file a ticket so that it doesn't get overlooked. Unless we announce a backwards-incompatible change, all changes are meant to not break things. The code itself is not catching all the right exceptions that can be raised: the idea was that if getdefaultlocale() returns something we can't use, it should just return no timezone. I'll give it another look and put in some more fallbacks. Regards, Malcolm -- Experience is something you don't get until just after you need it. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
