Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

Chris Angelico rosuav at gmail.com
Mon Mar 31 08:47:20 CEST 2014

On Mon, Mar 31, 2014 at 5:08 PM, Mark H Harris <harrismh777 at gmail.com> wrote:
> Unicode in python3.x is (mostly) working correctly. Congratulations to all
> who worked on it, hat is off.  The problem with unicode is that it is just a
> specification. The consortium cannot force or code anything. They control
> the scripts and make the specifications. It is left to *everyone* else to
> implement. And not everyone is taking on that task with the same gusto, if
> you follow my meaning.

Considering that Pike's native double-quoted string type stored true
Unicode (not UTF-16, not eight-bit, the full Unicode range) back in
1998, you're quite correct in saying that some take on that task with
more enthusiasm than others. Of course, that exact same fact does tell
against your other and more important point, namely that people were
unable to speak non-English to each other until very recently. Good


More information about the Python-list mailing list