I ran into this problem as well when I upgraded to the most recent django trunk. I found out about it because my tests failed the following error:
from locale import normalize ImportError: cannot import name normalize Whoever is writing the patch for ticket #5494 (http:// code.djangoproject.com/ticket/5494) _may_ want to take this into consideration. On Aug 16, 7:47 am, dcoy <[EMAIL PROTECTED]> wrote: > I figured this problem should occur in my windows environment as well. > So I did some tests but I never got that import problem. > In sys.path on windows the current dir is first (same on linux) so > python should start to look in the current dir for "locale". But > somehow the problem only arises on linux (which is running python 2.4, > windows is running 2.5, could that be it??) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
