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
bpo-47117: Don't crash if we fail to decode characters when the tokenizer buffers are uninitialized #32129
Conversation
…izer buffers are uninitialized
Testing this programatically is close to impossible :( |
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.
I also tried to write a test, but no luck on reproducing the same behavior. The changes LGTM
Co-authored-by: Batuhan Taskaya <isidentical@gmail.com>
@pablogsal: Status check is done, and it's a failure ❌ . |
@pablogsal: Status check is done, and it's a success ✅ . |
Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, @pablogsal, I could not cleanly backport this to |
GH-32130 is a backport of this pull request to the 3.10 branch. |
…e tokenizer buffers are uninitialized (pythonGH-32129) Automerge-Triggered-By: GH:pablogsal. (cherry picked from commit 26cca80) Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
https://bugs.python.org/issue47117
Automerge-Triggered-By: GH:pablogsal