Hi everyone, First I'd like to say I got bitten by this in the past. What worries me the most in the original report is the TEMPLATE_DEBUG part. IMHO, this should fail loudly regardless of any debug settings.
As for other stuff: On 22 January 2014 18:34, Ramiro Morales <[email protected]> wrote: > I think you are onto something re: the fact that we don't make clear > that our ugettext*() functions fail to accept encoded literals with > characters outside ASCII under Python 2.x. even when the encoding > metadata is correct. I think everyone is forgetting that those are *u*gettext() functions and they work fine with any literals as long as the argument type is unicode, because that is the only type they know how to handle. The implicit bytes->text conversion in Python 2 makes this a little less obvious, but the expected argument type is in the name. IMHO, It would be better for everyone if ugettext_lazy() and friends fail immediately when given anything other then text (unicode on Python 2, str on Python 3), but it's probably too late for that now. At least until Python 2 support is dropped completely. -- Łukasz Rekucki -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAEZs-E%2BVZ-Hnnm_%3D3Mx9XGS-xX9AfZZMEkAbWukhJf9yk0nvmw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
