text_combined: charles merriam cncnokdkvbyzfigmailcom hate bringing something hashed many times im bear little brain understanding migration path whole use 2to3 tools seems like abrupt hack workable causes serious plan near term 2x 3x migration id like present different view instead yelling must wrong consider far current migration path less rocky moving 26 30 appears encompass following major tasks minor ones 1 change unadorned strings default b default like illegal u 2 changed print becomes function 3 changed meaning keys items values changed 4 removed default ordering operators string exceptions old classes etc 5 changed repr long 6 completely predictable syntax modifications raise catch etc etc etc lot head even tool translate going cause odd warnings syntax errors everywhere especially hard advantages using 3x immediately realized upon conversion hopefully academic im hoping port bls metric code still consideration programmers would much prefer sequence could changes 26 done one module time way converted unconverted code could live side side time transitional elements would required build environment would want make changes gradually reasonable expectation first time ran 2to3 would also last biggest thoughtful cost carefully looking every single string application deciding bytes unicode adding b u adornment appropriately would take immense amount time requiring rethinking apis duplicating modules needing byte unicode processing etc something later expect transition period adorning strings whenever working code anyway eventually would enable python warning unadorned strings catch last cases times pull executable code file database socket would start banning deprecated changed names eg keys range input like makes sense might use iter_keys xrange raw_input doesnt would explicitly call functions use idioms perform old tasks range_as_list input_with_eval pattern period gradual change pulling compiler switch warn old usage would start using handy new printing function named print3 instead print statement might one day switch running 26 mode warns old style classes default comparators string exceptions like likely would use fine grained control turn warnings one time period weeks months could confidently run 2to3 build 3x version would amount work spread risk along much longer schedule options would save time using serendipity already maintaining code 26 version would always interact correctly modules upgraded many ways im saying anything new without fine grained control python would expect coders start running 3 option running 2to3 occasionally see would need fixed later module opened fine grained control could managed 80 way could done judicial control static analyzers pychecker pylint 100 would require options python overall 2x 3x transition needs fairly painless immediate features developers better unicode processing features items 26 eventually yet shown really useful perfect world gradual transition looks like like transition c code ansic code ansic compiled c compiler less like perl leaps version ready transition 27 30 would mechanical _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom wed 06 aug 2008 121516 0700 python3000 pep 3000 rethinking 2to3 __future__ migration path