[issue35417] Double parenthesis in print function running 2to3 in already correct call

Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed superseder: -> Close 2to3 issues and list them here ___ Python tracker ___

[issue35417] Double parenthesis in print function running 2to3 in already correct call

Paul Ganssle added the comment: > 2to3 is designed as a tool to convert a Python 2 code base to Python 3 at > once. I understand that once the code base is converted, you may want to > revert some unwanted "useless" changes. While this problem is likely to show up because someone has run

[issue35417] Double parenthesis in print function running 2to3 in already correct call

STINNER Victor added the comment: I suggest to close this issue as WONTFIX. 2to3 is designed as a tool to convert a Python 2 code base to Python 3 at once. I understand that once the code base is converted, you may want to revert some unwanted "useless" changes. Python 2 and Python 3

[issue35417] Double parenthesis in print function running 2to3 in already correct call

Karthikeyan Singaravelan added the comment: Thanks for the report. Is this similar to issue10375 ? One option would be to use -p to stop transforming print related code if you don't want to transform any print statement. $ cat /tmp/foo.py print (1) $ 2to3 /tmp/foo.py [snip] ---

[issue35417] Double parenthesis in print function running 2to3 in already correct call

New submission from Jonathan Alush-Aben : If 2to3 is run on a file with the following contents: a="string" print ("%s" % a) The output is: a="string" print (("%s" % a)) Although it was already a valid call to print in python3. -- components: 2to3 (2.x to 3.x conversion tool)