IronLanguages / IronLanguages/ironpython3
Incorrect messages for some `SyntaxError`s related to f-strings
Open
Nobody has claimed this yet.
CPython compatibility
What's New In Python 3.6
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
For example:
-
f'{lambda x:x}'reportsinvalid syntaxinstead ofunexpected EOF while parsing. Note thateval('(lambda x)')also reports the wrong message. -
eval("f'''{\xa0}'''")reportsinvalid syntaxinstead ofinvalid character in identifier(and the message is again different in 3.9). - eval("fu''") reports
invalid syntaxinstead ofunexpected EOF while parsing.
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 listed f-string and eval examples and compare IronPython's messages with the expected Python messages. Trace the syntax-error handling for these expressions; done means each example reports the specified message, including invalid character in identifier for the non-breaking-space case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100