[issue7141] 2to3 should add from __future__ import print_statement

Daniel Stutzbach report at bugs.python.org
Thu Sep 2 04:26:22 CEST 2010

Daniel Stutzbach <daniel at stutzbachenterprises.com> added the comment:

Well, I grant you that it's a bit of scope-creep, and if you want to reject it on those grounds I can't blame you.

To me it seems like a relatively small change that would greatly help people like myself who want to update older code so that it will run under 2.6, 2.7, and 3.1+.  Of course, since I don't know how to make the change, I could also be wrong about how easy it would be for a knowledgeable person to fit it into the existing 2to3 framework.


Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list