bpo-40334: regenerate metaparser as part of regen-all#19854
Merged
Conversation
gvanrossum
approved these changes
May 2, 2020
gvanrossum
left a comment
Member
There was a problem hiding this comment.
What brought about the desire to automatically regenerate the meta-parser?
Member
Author
Consistency with how we handle the rest of autogenerated files to know that they are up to date, more than anything. |
Member
|
Okay, sounds good.
|
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
4 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.
This PR does the following:
regen-pegentarget to the end of theregen-allso the changes inregen-tokenand are correctly picked up.regen-pegen-metaparserthat regenerates the metaparser (this means also that the CI will check that this file is updated from now on)regen-pegen-metaparsertoregen-allhttps://bugs.python.org/issue40334