It may, in fact, be necessary.  According to 
http://docs.python.org/py3k/whatsnew/3.0.html:

"It is not recommended to try to write source code that runs unchanged under 
both Python 2.6 and 3.0; you’d have to use a very contorted coding style, 
e.g. avoiding print statements, metaclasses, and much more. If you are 
maintaining a library that needs to support both Python 2.6 and Python 3.0, 
the best approach is to modify step 3 above by editing the 2.6 version of 
the source code and running the 2to3 translator again, rather than editing 
the 3.0 version of the source code."

Reply via email to