Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[3.13] gh-123229: Fix valgrind warning by initializing the f-string buffers to 0 in the tokenizer (GH-123263) #123264

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

Merged
merged 1 commit into from
Aug 23, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Aug 23, 2024

(cherry picked from commit adc5190)

Co-authored-by: Pablo Galindo Salgado [email protected]
Signed-off-by: Pablo Galindo [email protected]

…ffers to 0 in the tokenizer (pythonGH-123263)

(cherry picked from commit adc5190)

Co-authored-by: Pablo Galindo Salgado <[email protected]>
Signed-off-by: Pablo Galindo <[email protected]>
@pablogsal pablogsal enabled auto-merge (squash) August 23, 2024 12:34
@pablogsal pablogsal merged commit 935b8b4 into python:3.13 Aug 23, 2024
39 checks passed
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