[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Ammar Askar added the comment: > We should definitely document the column offset being 1-based Yes please, I remember working on that issue to make it consistently 1-based a while ago and I remember that the tooling was relying on 1-based indexes for column offsets. -- nosy:

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Guido van Rossum added the comment: We should definitely document the column offset being 1-based, if it hasn't been already. But be careful, there are some APIs that are 0-based and others that are 1-based, for column offsets. I was quite surprised at some point to find out that we were

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Terry J. Reedy added the comment: Before the patch, IDLE highlighted the \n endline with a red background, which tk displays as red background from the blank space after the 4 to the right edge of the text widget, including in 3.8.8. The 3.8 result, different from REPL, is due the the

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Change by Pablo Galindo Salgado : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Pablo Galindo Salgado added the comment: New changeset 994a519915bff4901abaa7476e2b91682dea619a by Miss Islington (bot) in branch '3.9': bpo-43555: Report the column offset for invalid line continuation character (GH-24939) (#24975)

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Change by miss-islington : -- nosy: +miss-islington nosy_count: 4.0 -> 5.0 pull_requests: +23734 pull_request: https://github.com/python/cpython/pull/24975 ___ Python tracker

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Pablo Galindo Salgado added the comment: New changeset 96eeff516204b7cc751103fa33dcc665e387846e by Pablo Galindo in branch 'master': bpo-43555: Report the column offset for invalid line continuation character (GH-24939)

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +23700 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24939 ___ Python tracker

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

Change by Karthikeyan Singaravelan : -- nosy: +gvanrossum, lys.nikolaou, pablogsal ___ Python tracker ___ ___ Python-bugs-list

[issue43555] Location of SyntaxError with new parser missing (after continuation character)

New submission from Andre Roberge : Normally, for SyntaxErrors, the location of the error is indicated by a ^. There is at least one case where the location is missing for 3.9 and 3.10.0a6 where it was shown before. Using the old parser for 3.9, or with previous versions of Python, the