martin v löwis qpnyslvloewisde recommended path porting python code python 30 use tool called 2to3 convert code python 2x code 3x code correct need support 2x 30 maintain code 2x code convert 3x code test make new release make two separate releases one 2x one 30 dont necessarily need two separate releases could make asingle source release 2to3 run users machines installation time many people working large set modules using direct svn checkouts development productsite need module discover bugs add features module also wildly varying experience levels python knowledge environment could run 2to3 even import time somebody proposed basically sort code change matter minor requires change test copy 2to3 test dance instead normal change test development cycle could remain changetest test runner would 2to3 conversion first end result people move python 3 long need sort thirdparty product plone collective similar set modules going much work everybody stay 2x means incentive port thirdparty products 30 becomes chicken egg catch 22 problem think problem highly theoretical even enduser application ported 30 within first year still time 32 released major library packages available best case means python 3 dies nobody uses yes best case horrible case agree worst case community splits two dangerous python whole python may survive split two communities would negative community whole zope problem zope 2 zope 3 think unfounded fears hope clarifies things thanks still think use 2to3 cases youve described regards martin _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom wed 06 aug 2008 122410 0500 python3000 utext alias text