[issue35260] 2to3 Parse Error on Python 3 print() with arguments

Mark Dickinson added the comment: Closing. 2to3 is working as designed here. -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

Mark Dickinson added the comment: I'm still confused: the main purpose of 2to3 is to take Python 2 code and turn it into Python 3 code. The docs[1] are fairly unambiguous here: > 2to3 is a Python program that reads Python 2.x source code and applies a > series of fixers to transform it into

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

batterystaple456 added the comment: I was expecting that like other Python 3 code, since it is already in Python 3, it would not parse it like Python 2. -- ___ Python tracker ___

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

Mark Dickinson added the comment: I'm not sure I understand the report: 2to3 expects a valid Python 2 file as input, and the file a.py isn't a valid Python 2 file: the `print` line is a SyntaxError in the absence of a `from __future__ import print_function`. So yes, this *is* being treated l

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

Change by batterystaple456 : -- type: compile error -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue35260] 2to3 Parse Error on Python 3 print() with arguments

New submission from batterystaple456 : File a.py: print("foo", end='bar') # ParseError I think the error is caused by arguments in the Python 3 print() function (e.g. end, sep) that are not ignored by 2to3, and (possibl