IronLanguages / IronLanguages/ironpython3
SyntaxError: (unicode error) messages are missing byte positions
Open
Nobody has claimed this yet.
CPython compatibility
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
For example, "\N" reports
SyntaxError: (unicode error) malformed \N character escape
instead of
SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 0-1: malformed \N character escape
This also affects the f-string versions (f"\N").
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported SyntaxError examples for both regular and f-string forms, then locate the IronPython code that formats unicode error messages. Compare the output with the expected codec, byte-position, and malformed-escape details; done means both examples report the missing byte positions consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100