-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
zstd should use Py_XSETREF #134885
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
Labels
3.14
bugs and security fixes
3.15
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
type-bug
An unexpected behavior, bug, or error
Comments
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 29, 2025
encukou
pushed a commit
that referenced
this issue
May 30, 2025
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 30, 2025
(cherry picked from commit 45c6c48) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
cc @emmatyping (the fix is already merged, but I just thought you'd want to be aware of it) |
Thank you for the fix! |
Yes thank you! TIL about |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
3.14
bugs and security fixes
3.15
new features, bugs and security fixes
extension-modules
C modules in the Modules dir
type-bug
An unexpected behavior, bug, or error
Uh oh!
There was an error while loading. Please reload this page.
Bug report
Bug description:
There is a theoretical crash path in the new zstd module that can be avoided with Py_XSETREF. PR incoming.
CPython versions tested on:
CPython main branch
Operating systems tested on:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: