-
-
Notifications
You must be signed in to change notification settings - Fork 33.9k
bpo-36440: include node names in ParserError messages, instead of numeric IDs #12565
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
Conversation
Misc/NEWS.d/next/Core and Builtins/2019-03-25-13-45-19.bpo-36440.gkvzhi.rst
Outdated
Show resolved
Hide resolved
|
You have some trailing whitespace in |
7de4a23 to
f6601c5
Compare
serhiy-storchaka
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if the index out of the boundary of the array?
f6601c5 to
127ff2f
Compare
Fixed |
127ff2f to
e204705
Compare
e204705 to
19ced03
Compare
|
@pablogsal do you have any unresolved comments regarding this patch? |
|
@tyomitch Thanks for the ping and sorry for the delay! |
|
Thanks @tyomitch for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
Sorry, @tyomitch and @pablogsal, I could not cleanly backport this to |
|
GH-12671 is a backport of this pull request to the 3.7 branch. |
…of numeric IDs (pythonGH-12565) The error messages in the parser module are referring to numeric IDs for the nodes. To improve readability, use the node names when reporting errors.. (cherry picked from commit cb0748d) Co-authored-by: tyomitch <tyomitch@gmail.com>
https://bugs.python.org/issue36440