{{ message }}
bpo-40334: Do not show error caret if RAISE_SYNTAX_ERROR_NO_COL_OFFSE…#20020
Closed
pablogsal wants to merge 1 commit into
Closed
bpo-40334: Do not show error caret if RAISE_SYNTAX_ERROR_NO_COL_OFFSE…#20020pablogsal wants to merge 1 commit into
pablogsal wants to merge 1 commit into
Conversation
pablogsal
commented
May 10, 2020
Member
Author
|
Wow, I am confused about this failing test in that expects that the caret is on the first character but the error in |
Sorry, something went wrong.
Member
That's a bug. The old parser puts the caret at the start of the "target". Example: |
Sorry, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.
Before:
With this PR:
https://bugs.python.org/issue40334