bpo-40334: Improve column offsets for thrown syntax errors by Pegen#19782
bpo-40334: Improve column offsets for thrown syntax errors by Pegen#19782pablogsal merged 4 commits into
Conversation
lysnikolaou
left a comment
There was a problem hiding this comment.
Thanks @isidentical for spending time on this! It's a really nice improvement.
Sorry, something went wrong.
|
@isidentical there's a merge conflict -- you need to merge master and run |
Sorry, something went wrong.
Best way of fixing a bug! 🎉 |
Sorry, something went wrong.
|
The travis target is stucked, closing and reopening to re-trigger the CI |
Sorry, something went wrong.
|
Hummm, there is a bunch of warnings now after the last rebasing: @isidentical could you take a look? Seems that we are passing the error message incorrectly with this PR |
Sorry, something went wrong.
Yup, this PR changes signature of _PyPegen_raise_error. I missed that usage when I rebased. Now, it should be fixed. |
Sorry, something went wrong.
I've been trying to figure out a good way to handle
ast.cerrors, but no luck so far. I've splitted them to their own test and fixed remaining offset errors to ensure full compatibility with the old parser.https://bugs.python.org/issue40334