On Dec 19, 7:47 pm, Rajesh Dhawan <[EMAIL PROTECTED]> wrote:
> > As I mentioned in my other post, it doesn't work for the one process.
>
> My previous code snippet missed an important statement. You will need
> to first get an instance of _transactions from trans_real.py before
> you declare it to be global. So, check if something like this helps:
>
> from django.utils import translation
> translation.deactivate_all()
> _translations = translation.trans_real._translations # <--- Note this
> globals _translations
> _translations = {}
> from datetime import datetime
> globals _translations_loadtime
> _translations_loadtime = datetime.now()
> translation.activate(<translation language >)
>
Tried the above, but _translations is still getting repopulated
somewhere and won't pick up the new translations.
> <snip>
> James Bennett has a nice article about server startup in which one
> section talks about registries. It might be worth it to peruse that
> even though it doesn't directly address this problem.
>
> See:http://www.b-list.org/weblog/2007/nov/05/server-startup/
Useful information, thanks.
James
>
> -Rajesh
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
