-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-41044: generate a valid python parser for opt+seq rules #20995
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
Conversation
# Note trailing comma (if there isn't already one, | ||
# which can occur when rules have both repeat0 and optional | ||
# marker, e.g: [rule*]) | ||
if call.endswith(","): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hummmm, not a find on relying on the generated code to reason about the grammar structure (I know that we do it in other places but we have been removing those as it makes it more difficult to reason about). In this case I have to say that is pretty straightforward so it may be fine.
Co-authored-by: Pablo Galindo <[email protected]>
Thanks @isidentical for the PR, and @pablogsal for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9. |
…nGH-20995) Co-authored-by: Pablo Galindo <[email protected]> (cherry picked from commit 55460ee) Co-authored-by: Batuhan Taskaya <[email protected]>
GH-21008 is a backport of this pull request to the 3.9 branch. |
) Co-authored-by: Pablo Galindo <[email protected]> (cherry picked from commit 55460ee) Co-authored-by: Batuhan Taskaya <[email protected]>
…nGH-20995) Co-authored-by: Pablo Galindo <[email protected]>
…nGH-20995) Co-authored-by: Pablo Galindo <[email protected]>
https://bugs.python.org/issue41044