-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
gh-123229: Fix valgrind warning by initializing the f-string buffers to 0 in the tokenizer #123263
Conversation
pablogsal
commented
Aug 23, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: New valgrind warning in Python 3.12.5 #123229
…ffers to 0 in the tokenizer Signed-off-by: Pablo Galindo <[email protected]>
Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…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]>
GH-123264 is a backport of this pull request to the 3.13 branch. |
Sorry, @pablogsal, I could not cleanly backport this to
|
GH-123265 is a backport of this pull request to the 3.12 branch. |
…ring buffers 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]>
…uffers to 0 in the tokenizer (GH-123263) (#123264) gh-123229: Fix valgrind warning by initializing the f-string buffers to 0 in the tokenizer (GH-123263) (cherry picked from commit adc5190) Signed-off-by: Pablo Galindo <[email protected]> Co-authored-by: Pablo Galindo Salgado <[email protected]>
…uffers to 0 in the tokenizer (GH-123263) (#123265) (cherry picked from commit adc5190) Signed-off-by: Pablo Galindo <[email protected]>
|