GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||
GeezerVison is showing github.com — gh-156894: Fix the position of syntax errors which cover a range by serhiy-storchaka · Pull Request #156901 · python/cpython Conversation
Member
>>> compile("abcd = 00010", "<t>", "exec") # before and after File "<t>", line 1 abcd = 00010 ^^^ >>> compile("αβγδ = 00010", "<t>", "exec") # before File "<t>", line 1 αβγδ = 00010 ^ >>> compile("αβγδ = 00010", "<t>", "exec") # after File "<t>", line 1 αβγδ = 00010 ^^^ The conversion is done in
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsThe callers of _PyTokenizer_syntaxerror_known_range() pass columns in bytes, but SyntaxError.offset and end_offset are columns in characters. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
serhiy-storchaka
requested review from
iritkatriel,
lysnikolaou and
pablogsal
as code owners
grayjk
reviewed
|
| ('\u03b1\u03b2\u03b3\u03b4 = 00010', 8, 11), | |
| ('\u03b1\u03b2\u03b3\u03b4 = 00010', 8, 11), | |
| ('e\u0301'*4 = 00010', 8, 11), |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It counts code points, not visible width.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
There was an error while loading. Please reload this page.
|
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Sorry, @serhiy-storchaka, I could not cleanly backport this to |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156926 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156927 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156928 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…ge (GH-156901) (GH-156928) The callers of _PyTokenizer_syntaxerror_known_range() pass columns in bytes, but SyntaxError.offset and end_offset are columns in characters. (cherry picked from commit 59a6913) Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
…ge (GH-156901) (GH-156927) The callers of _PyTokenizer_syntaxerror_known_range() pass columns in bytes, but SyntaxError.offset and end_offset are columns in characters. (cherry picked from commit 59a6913) Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
pythonGH-156901) The callers of _PyTokenizer_syntaxerror_known_range() pass columns in bytes, but SyntaxError.offset and end_offset are columns in characters. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
…ge (GH-156901) (#156926) The callers of `_PyTokenizer_syntaxerror_known_range()` pass columns in bytes, but `SyntaxError.offset` and `end_offset` are columns in characters. (cherry picked from commit 59a6913) Co-authored-by: Serhiy Storchaka <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.