ast.parse produces different (lineno, col_offset) in some cases

Open
#746 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, python
Domain
compilers

Research direction

Start with the offset-related cases in Tests/test_ast.py and reproduce the reported ast.parse example, comparing IronPython with CPython. Investigate the other differing (lineno, col_offset) cases and consider the work complete when the relevant tests match CPython behavior.

Written by the indexing model from the issue text.

Description

core CPython compatibility

For example:

ast.parse("if v:pass\r\nelif 1: pass").body[0].orelse[0].col_offset

is 5 with CPython and 0 with IronPython.

There are a number of other cases of this in Tests/test_ast.py that should be investigated.

Related to: https://github.com/IronLanguages/ironpython3/pull/744

Dominant language
C#
Stars
2.8k
Forks
316
Avg merge
1d 9h
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IronLanguages/ironpython3

All issues in IronLanguages/ironpython3

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.