martin v löwis qpnyslvloewisde encouraged __3x guidelines__ presume although ive found yet kind document developers titled something like migrate python code 2x 3x document would logical place advice consideration tradeoffs jumping 3x maintaining two synced versions using 2to3 3to2 risks keeping two independent releases identifying best practices would help make good choices community dont think core committers qualified write document instead would written people actually ported project 2 3 form say document couldnt part 3k release shouldnt reviewed core committers also might turn core committers writes document theoretical background could work projects would lot like books giving advise written people never followed advise never chance dont actual success story dualversion distribution even prototype using 2to3 within distutils package would encourage practice without least one example dont success story python 3 period nobody ever attempted run significant code base python 3 test suite afaik always worked fine see reason fix first place pardon lack knowledge background say always worked fine referring personal experiences using _install_ software experiences packager actually distributing complex collections modules different platforms ive maintaining larger project pyxml several years writtenmaintained smaller projects iconv partial pythonfam used distutils also extended distutils core upload bdist_msi commands experience installing distutilsbased packages usually pleasant although prefer use debian package available regards martin _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom wed 06 aug 2008 112820 0500 pythondev breaking distutils pypi python 3000