Incorrect f-string parsing#112
Merged
Merged
Conversation
Member
|
Thank you. Could you also open a PR to RustPython/RustPython using this PR to ensure it doesn't break RustPython build? |
Contributor
Author
|
I've opened PR to ensure that RustPython builds don't fail. |
youknowone
approved these changes
Jan 23, 2024
youknowone
left a comment
youknowone
left a comment
Member
There was a problem hiding this comment.
Thank you so much. If you are interested in fixing parser bugs, backporting Ruff's python parser to RustPython would be a one-shot solution
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#88
I've fixed to parse escaped brackets correctly.