Repository navigation
Invalid error range when the tokeniser finds invalid bytes #115823
Description
When the tokeniser raises errors due to invalid byte sequences only when the parser encoding is implicit (such when parsing a file), the error locations are not properly transformed to character offsets
Linked PRs
- gh-115823: Calculate correctly error locations when dealing with implicit encodings #115824
- [3.12] gh-115823: Calculate correctly error locations when dealing with implicit encodings (GH-115824) #115949
- [3.11] gh-115823: Calculate correctly error locations when dealing with implicit encodings (GH-115824) #115950
Activity
pythongh-115823: Calculate correctly error locations when dealing wit…
fixup! pythongh-115823: Calculate correctly error locations when deal…
gh-115823: Calculate correctly error locations when dealing with impl…
pythongh-115823: Calculate correctly error locations when dealing wit…
pythongh-115823: Calculate correctly error locations when dealing wit…
[3.12] gh-115823: Calculate correctly error locations when dealing wi…
[3.11] gh-115823: Calculate correctly error locations when dealing wi…
pythongh-115823: Calculate correctly error locations when dealing wit…
pythongh-115823: Calculate correctly error locations when dealing wit…
pythongh-115823: Calculate correctly error locations when dealing wit…
pythongh-115823: Calculate correctly error locations when dealing wit…