thomas wouters fgxflgpythonorg sun mar 23 2008 837 lennart regebro wrote eric smith wrote implementable work occur astc see py_unicodeflag cant occur later need skip encoding done parsestr __future__ import interpreted ast built time encoding already applied radical things could work around would gigantic change oh dont believe true simply store source encoding information might already translate use string literals unicodeliteral encoding still think bad idea using codebase 30 26 leave inefficient fragile code one two codebases quite likely know ive tried dont see improves maintainability leave source full forward backwardcompatibility hacks 30 meant clean break please treat yes means cant run source tree two different python versions bad means adding compilationstyle step one two python versions bad quite easily automated proven vast majority programming languages need step anyway howver 26 doesnt support end world turn necessary 27 could always released dont know large codebases like twisted zopeplone world isnt likely even try moving 30 time soon final release since complicated probably wait support turns needed always assumption also idea 26 27 would much rather 30 isnt widely accepted years longer cluttered backward compatibility crap even rather widely used code riddled guido end thomas wouters hi im signature virus copy signature file help spread wed 06 aug 2008 215607 0100 pythondev proposal __future__ import unicode_string_literals