talin ovijnacmorg short discussion python 30 porting biweekly python meeting google suggested write discussed reading python 3000 mailing list last several months apparent many different approaches making transition 26 30 approaches involve sourcetosource translation using 2to3 tool couple different strategies discussed forum others maintaining two parallel branches application one 26 one 30 using 2to3 keep sync maintaining two parallel branches application manually applying fixes branches without synchronizing using 2to3 generate time 30 version needed development work 26 branch also discussion 3to2 tool would reversemigrate code 30 26 could potentially much simpler tool 2to3 since many obscure cases 2to3 would handle new code however alternative strategy doesnt involve 2to3 write code greatest common subset 26 30 lennart regbro pointed earlier common subset actually quite large larger guido originally intended think write fairly substantial applications ability turn default unicode strings permodule basis one last hurdles effective programming dialect python removed writing code subset dialect take care however many modules standard library slightly different semantics 30 compared 26 dealt simply avoiding legacy apis others handled creating library utility functions isolate differences underlying python implementation part general effort document various 30 porting strategies would like see document describing common subset write programs doesnt complete standalone manual addendum regular python docs explaining things avoid get around document could include description extra credit implementation utility library mentioned earlier isolates difference two python versions volunteers talin _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom wed 06 aug 2008 180315 0700 python3000 python 30 porting strategies