Articles on akshansh's Blog

Week 12 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 10 Sep 2022 11:32:56 +0000

Tasks Accomplished This Week

Issues Closed

Tokenizer error in the string · Issue #1023 · lcompilers/lpython (github.com) [CLOSED]
Do not allow mixed (spaces & tab) indent · Issue #974 · lcompilers/lpython (github.com) [CLOSED]

PRs Merged

[Parser] Fix a bug in tokenizer related to docstring by akshanshbhatt · Pull Request #1068 · lcompilers/lpython (github.com) [MERGED]
[Parser] Fix issue with different indentation type within the same file by akshanshbhatt · Pull Request #1070 · lcompilers/lpython (github.com) [MERGED]
[Parser] Fix a bug with indentation of blocks by akshanshbhatt · Pull Request #1078 · lcompilers/lpython (github.com) [MERGED]

Week 11 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sun, 28 Aug 2022 11:00:55 +0000

Tasks Accomplished This Week

Issues Closed

PRs Merged

Week 10 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Mon, 22 Aug 2022 09:05:58 +0000

Tasks Accomplished This Week

Issues Closed

PRs Merged

Week 9 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sun, 14 Aug 2022 14:53:53 +0000

Tasks Accomplished This Week

Issues Closed/Partially Completed

Non-ascii name is not recognized by both the parser · Issue #916 · lcompilers/lpython (github.com) [OPEN]

PRs

Issues Faced This Week

While working for an optimised version of the formatted string (using the tokeniser itself), I faced multiple issues. For now, it is still a work in progress.

Week 8 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Fri, 05 Aug 2022 13:36:35 +0000

Tasks Accomplished This Week

Issues Closed/Partially Completed

PRs

Week 7 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 30 Jul 2022 09:59:39 +0000

Tasks Accomplished This Week

Issues Closed/Partially Completed

PRs

Week 6 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Fri, 22 Jul 2022 16:43:43 +0000

Tasks Accomplished This Week

Issues Raised

Issues Closed/Partially Completed

PRs

Week 5 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 16 Jul 2022 09:22:50 +0000

Tasks Accomplished This Week

Issues Closed/Partially Completed

Merged PRs

Problems Faced This Week

While working on making the BoolOp node have multiple values of expr type, I faced numerous issues. I could not make it match the output from the current parser. Thirumalai and I collaboratively worked on it and overcame most of the problems. It is mostly complete and requires some minor changes before submitting the final patch.

Plans For Upcoming Week

The new parser still generates many errors I found while testing on Python files from NumPy and SymPy repos. I will open issues related to each of these errors and fix them. One good sign I noticed was that whatever AST the new parser generates (after commenting out the error causing part) is highly accurate compared to the existing one.

Week 4 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 09 Jul 2022 18:19:08 +0000

Tasks Accomplished This Week

Issues Raised

[Parser] `Tokenizer Error` on list comprehension example · Issue #752 · lcompilers/lpython (github.com) [OPEN]

Issues Closed/Partially Completed

PRs

Problems Faced This Week

I didn't face any major problems this week.

Plans For Upcoming Week

Most of the major AST nodes are implemented now. I plan to rigorously test the new parser to its limit by parsing python files from some of the major Python projects' repos such as SymPy and NumPy.
Comparing the AST generated by the new parser from that of the existing parser would let us know the changes to be made in the current parser generator file.

Week 3 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 02 Jul 2022 14:57:50 +0000

Tasks Accomplished This Week

Issues Raised

Issues Closed/Partially Completed

PRs

Problems Faced This Week

While working on making tuples a valid valid expr component, I faced multiple challenges. I even discussed it with my mentor (@Thirumalai) but as of now, there is no progress on this part.

Plans For Upcoming Week

I aim to work on the existing issues with Parser label.

Week 2 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 25 Jun 2022 09:03:37 +0000

Tasks Accomplished This Week

Issues Raised

[Parser] Expression tree is not properly generated in `FormattedValue` · Issue #641 · lcompilers/lpython (github.com) [OPEN]

Issues Closed/Partially Completed

PRs

Problems Faced This Week

Only major problem faced this week was issue #641, which I plan to solve in the upcoming weeks.

Plans For Upcoming Week

I aim to work on issues #507, #512, #620.

Week 1 - Progress Report

qaz.akshansh@gmail.com (akshansh) — Sat, 18 Jun 2022 13:19:23 +0000

Tasks Accomplished This Week

Issues Raised

Issues Closed/Partially Completed

PRs

Problems Faced This Week

I tried to close #511 altogether but failed to do so because of multiple shift/reduce conflicts raised during parser generation. The syntax for logical keyword in was conflicting with the syntax of for loop.
While working on parsing prefixed strings, I came across an error with byte strings. The current AST generation (the current slow parser) needs to be debugged.
Formatted strings, as of now, works well for most of the cases. However in some cases, there is gibberish character generation for the formatted value's id field. I have still not found the actual cause of this issue. The same example generates perfectly fine AST on my mentor's computer (Linux, x86) but causes issue on mine (MacOS, ARM).

Plans For Upcoming Week

I aim to complete PR #624 and close the issue related to it (#512). I aim to add basic parsing support for formatted, byte, raw and unicode string initially. We can iterate and make it better later.
I also aim to work on issues #508 and #620.
I will try to finally close #511 by refactoring the for loop parsing patterns.