[Zope3-dev] i18n, unicode, and the underline

[Guido van Rossum]

> That still leaves the literal string "hole", and IMHO it's a really big 
> hole.  Three methods have been suggested for patching this hole: 
> prefixing all literal strings with "u", calling the unicode() builtin in 
> code that concatenates strings, or using 'python -U'.  Since 'python -U' 
> doesn't quite work, we only have the first two options for now, and both 
> are a burden for the programmer.  One requires uglifying the source, and 
> the other requires deeper knowledge than we wanted to require of 
> programmers.  Ouch.

I've forgotten the context...  Why you would want string manipulation
functions to return Unicode even when the result can be expressed as
ASCII?

--Guido van Rossum (home page: http://www.python.org/~guido/)