Wiadomość napisana w dniu 2009-08-13, o godz. 04:31, przez Malcolm Tredinnick:
>> As translation.activate() is process-wide, this approach is not >> safe in multithreaded environment if using static translation (not >> request-based). > > This is not correct. The translation.activate() call is thread- > specific > and definitely thread-safe. Otherwise Django's entire translation > infrastructure wouldn't work. Hmmm. Must be some kind of race condition in mod_python... Anyway, I was wrong, activate() is thread safe. -- Artificial intelligence stands no chance against natural stupidity Jarek Zgoda, R&D, Redefine jarek.zg...@redefine.pl --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
