Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tentative fix for issue #437. #440

Merged
merged 1 commit into from
Apr 9, 2023
Merged

Tentative fix for issue #437. #440

merged 1 commit into from
Apr 9, 2023

Conversation

andrem-eberle
Copy link
Contributor

@andrem-eberle andrem-eberle commented Apr 8, 2023

I followed your guidelines, and reworked ifelsestmt.py a bit. I just added another set of rules that is then checked for offsets, it fixed this particular issue (#437) at least. I know the tests in test/ aren't great, but at least they aren't failing :)

I ran the tests on test/stdlib/runtests.sh also (Python 2.7) but I keep getting an error, which I included in issue #439. I might look into that one also since I am working on it.

…t.py to check against for offsets. Seems to have fixed current issue. The result output is switching nested if-else-if-else-etc to a chain of if-elif-elif now, but semantically seems correct.
@rocky
Copy link
Owner

rocky commented Apr 9, 2023

LGTM - this was the kind of change I was expecting in the back of my mind. Thanks!

@rocky rocky merged commit cd00499 into rocky:master Apr 9, 2023
@rocky rocky mentioned this pull request Apr 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants