You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
(🐞) Column marker in error message off when line contains non ASCII character #102310
Can confirm on Python 3.12.0a5+ (heads/main:bcadcde712, Feb 26 2023, 12:54:46) [MSC v.1929 64 bit (AMD64)] on win32.
Note: Ā here is UTF8-encoded as C4 80 (a single U+0100 LATIN CAPITAL LETTER A WITH MACRON). So incorrect row advancing on combined code points is totally ruled out until text normalization happens inside the parser.
changed the title [-](🐞) Column marker in error message off for bytes with non ASCII character[/-][+](🐞) Column marker in error message off when line contains non ASCII character[/+]on Feb 28, 2023
In IDLE, Python 3.12.0a5+ (heads/main:0f89acf6cc, Feb 27 2023, 21:33:28) says "incomplete input" for this and "\N{a}", reported in #102312, and marks the closing quote, but this is effect of how codeop compiles.
In REPL, I see the above and the #102312 message. I closed #102312 as duplicate.
Activity
arhadthedev commentedon Feb 28, 2023
Can confirm on
Python 3.12.0a5+ (heads/main:bcadcde712, Feb 26 2023, 12:54:46) [MSC v.1929 64 bit (AMD64)] on win32.Note:
Āhere is UTF8-encoded asC4 80(a single U+0100 LATIN CAPITAL LETTER A WITH MACRON). So incorrect row advancing on combined code points is totally ruled out until text normalization happens inside the parser.[-](🐞) Column marker in error message off for bytes with non ASCII character[/-][+](🐞) Column marker in error message off when line contains non ASCII character[/+]arhadthedev commentedon Feb 28, 2023
@benjaminp, @pablogsal (as parser experts)
update: @gvanrossum, @lysnikolaou (as new parser experts)
terryjreedy commentedon Feb 28, 2023
In IDLE, Python 3.12.0a5+ (heads/main:0f89acf6cc, Feb 27 2023, 21:33:28) says "incomplete input" for this and
"\N{a}", reported in #102312, and marks the closing quote, but this is effect of how codeop compiles.In REPL, I see the above and the #102312 message. I closed #102312 as duplicate.
terryjreedy commentedon Feb 28, 2023
Verified bug in installed 3.10.10, 3.11.2, and 3.12.a5.
sobolevn commentedon Feb 28, 2023
What do you think about this?
This can be achieved with:

Or do we need to highlight the symbol exactly?
If my solution is fine, I can add a test case and send a PR.
arhadthedev commentedon Apr 21, 2023
@sobolevn In absence of other feedback, your solution looks better than nothing. So it's worth to create a PR and get it merged before 3.12b1.
sobolevn commentedon Apr 21, 2023
Will do :)
pythongh-102310: Change error range for invalid bytes literals
gh-102310: Change error range for invalid bytes literals (#103663)
pythongh-102310: Change error range for invalid bytes literals (pytho…
[3.11] gh-102310: Change error range for invalid bytes literals (GH-1…
lysnikolaou commentedon Apr 25, 2023
Can this be closed?
Edit: Actually, I'm closing this. Re-open in case there's more to it.