Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-34013: Don't consider a grouped expression when reporting legacy print syntax errors #27521

Merged
merged 1 commit into from Aug 1, 2021

Conversation

pablogsal
Copy link
Member

@pablogsal pablogsal commented Jul 31, 2021

@pablogsal
Copy link
Member Author

pablogsal commented Jul 31, 2021

@brandtbucher Could you review this at the earliest convenience? I would like to land this before the end of tomorrow so I can release the rc on schedule.

Copy link
Member

@brandtbucher brandtbucher left a comment

Thanks for the quick fix!

@pablogsal pablogsal merged commit 208a7e9 into python:main Aug 1, 2021
12 checks passed
@pablogsal pablogsal deleted the bpo-34013 branch Aug 1, 2021
@miss-islington
Copy link
Contributor

miss-islington commented Aug 1, 2021

Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10.
🐍🍒🤖

@bedevere-bot
Copy link

bedevere-bot commented Aug 1, 2021

GH-27522 is a backport of this pull request to the 3.10 branch.

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Aug 1, 2021
…print syntax errors (pythonGH-27521)

(cherry picked from commit 208a7e9)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
miss-islington added a commit that referenced this pull request Aug 1, 2021
…print syntax errors (GH-27521)

(cherry picked from commit 208a7e9)

Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants