Repository navigation
Conversation
…unclosed replacement field
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
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.
Fixes a regression from the 3.15 backport of gh-157778 (#158047).
When a nested f-string ends while one of its
{is still open, that{stays on the lexer's bracket stack. The backport worked out the position of the outer f-string's{from the current bracket count, so the extra{made it point at the wrong entry.The fix saves the bracket level when the f-string starts and uses it instead, which is what main does.
tok->parenstack[level] == '{'fails on 3.15 for a nested f-string whose format spec ends in a backslash #162140