terry reedy twhvuyludeledu martin v lwis wrote message news47e782261070607vloewisde think agree would like plone migrate 3x without much pain collective situation may difficult migration others httpwikipythonorgmoinportingdjangoto3k repeat patch django support versions python simultaneously 2x 30 find surprising two reasons 1 impression discussions past year fully automatic use 2to3 would presume use 26 backported 30 features __future__ imports really works ealier 2x code great please pardon initial surprise scepticism 2 report caveats certainly large parts code base havent touched issues likely show port attempts maintain compatibility older python versions single code base goal support versions django supports plus 30 current patch fails certain details due bugs 2to3 tool approach mostly works following flaws fixers work incorrectly bugs 2453 2446 2468 worked sqlite3 databases tested unqualified assertion seems like anticipated future certain maybe others present reality 3 also said worked around 2to3 failings conditional blocks like presume following sysversion 300 else assume correctly rather 2to3 2to3 remove wrapper leave 30 code would someone go thru hand get clean 30 code understand standard method multiple release code seems bit like cheating since point 2to3 converting typesclasstype types future fixer item terry wed 06 aug 2008 183418 0400 pythondev proposal __future__import unicode_string_literals