On 9/23/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Previously, I've wondered about pulling string_concat out of trans_real > and into __init__, since it doesn't depend on the USE_I18N setting at > all. That piece of tidying would avoid some of these problems, too, so I > think I'll do that as well.
Makes a lot of sense. > string_concat is the essentially lazy version of Python's standard > string.join. We don't want the results -- the pieces being joined -- to > be coerced to unicode or str objects until we are ready to display them, > because what they produce is dependent on the current locale setting. Ah, of course. I hadn't considered the possibility of changing locales while running. Cheers, Andrew. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
