[issue36122] Second run of 2to3 continues to modify output

Change by Terry J. Reedy : -- resolution: -> not a bug type: enhancement -> behavior ___ Python tracker ___ ___ Python-bugs-list ma

[issue36122] Second run of 2to3 continues to modify output

bers added the comment: Yes, understood! Thanks for the explanation. -- stage: -> resolved status: open -> closed ___ Python tracker ___ _

[issue36122] Second run of 2to3 continues to modify output

Paul Ganssle added the comment: Because what's being printed is a tuple, I think it's not exactly the same as issue35417, because in fact this is the correct behavior for 2to3, note that in Python 2: Python 2.7.15 (default, Jul 21 2018, 11:13:03) >>> print 1, 2 1 2 >>> print(1, 2) (1, 2)

[issue36122] Second run of 2to3 continues to modify output

Karthikeyan Singaravelan added the comment: This seems to be same as issue35417 and some resolution on detecting these type of cases at issue10375. -- nosy: +benjamin.peterson, xtreak ___ Python tracker ___

[issue36122] Second run of 2to3 continues to modify output

New submission from bers : I did this on Windows 10: P:\>python --version Python 3.7.2 P:\>echo print 1, 2 > Test.py P:\>python Test.py File "Test.py", line 1 print 1, 2 ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(1, 2)? P:\>2to3 -w Test.py Refac