IronLanguages / IronLanguages/ironpython3
`eval` of a string starting with a blank line raises `SyntaxError`
Open
Nobody has claimed this yet.
builtins
CPython compatibility
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
The following succeeds with CPython:
# should not throw
eval(" 3.14") # OK
eval("\t3.14") # OK
eval("\n3.14") # raises SyntaxError in ipy
# should raise SyntaxError
try: eval("\n 3.14")
except SyntaxError: pass # OK
else: assert False
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 running the issue's eval reproduction and tracing the eval entry point in IronPython. Compare the behavior with CPython, then add a regression test covering the accepted blank-line case and the SyntaxError case; done means both examples match CPython.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100