lezer/python
1
0
Fork 0
Code Issues 1 Pull requests Activity

support python3 print statements as print instead of regular function… #12

Closed
wagslane wants to merge 1 commit from main into main
pull from: main
merge into: lezer:main
Conversation 2 Commits 1 Files changed 5 +6 -5
wagslane commented 2022-11-11 17:49:15 +01:00 (Migrated from github.com)
Copy link

Most modern editors highlight the "python" part of a Python 3 function call like a keyword, not a normal call expression.

This supports both Python3 and Python 2 now, instead of just legacy.

Most modern editors highlight the "python" part of a Python 3 function call like a keyword, not a normal call expression. This supports both Python3 and Python 2 now, instead of just legacy.
marijnh commented 2022-11-11 20:45:31 +01:00 (Migrated from github.com)
Copy link

The way I understand it, print is a regular built-in function in Python 3, and not something that actually appears in the grammar. As such, I feel the current behavior is more appropriate.

The way I understand it, `print` _is_ a regular built-in function in Python 3, and not something that actually appears in the grammar. As such, I feel the current behavior is more appropriate.
wagslane commented 2022-11-11 21:10:04 +01:00 (Migrated from github.com)
Copy link

Code mirror 5 didn't work this way, and neither does VS code. It results in
really bland looking print statements that aren't recognizable.

On Fri, Nov 11, 2022, 12:45 PM Marijn Haverbeke @.***>
wrote:

The way I understand it, print is a regular built-in function in Python
3, and not something that actually appears in the grammar. As such, I feel
the current behavior is more appropriate.

—
Reply to this email directly, view it on GitHub
https://github.com/lezer-parser/python/pull/12#issuecomment-1312137206,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFHZKVJSFSM7GD3UGWAEN33WH2O6NANCNFSM6AAAAAAR5YMMOA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Code mirror 5 didn't work this way, and neither does VS code. It results in really bland looking print statements that aren't recognizable. On Fri, Nov 11, 2022, 12:45 PM Marijn Haverbeke ***@***.***> wrote: > The way I understand it, print *is* a regular built-in function in Python > 3, and not something that actually appears in the grammar. As such, I feel > the current behavior is more appropriate. > > — > Reply to this email directly, view it on GitHub > <https://github.com/lezer-parser/python/pull/12#issuecomment-1312137206>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFHZKVJSFSM7GD3UGWAEN33WH2O6NANCNFSM6AAAAAAR5YMMOA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lezer/python!12
No description provided.