🌐 AI搜索 & 代理 主页
Skip to content

gh-142606: Fix extra NULL arguments passed to PyObject_CallFunction #142607

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.

Sign up for GitHub

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

Open
hyongtao-code wants to merge 2 commits into
base: main
Choose a base branch
from
+5 −2
Open

gh-142606: Fix extra NULL arguments passed to PyObject_CallFunction #142607

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be078a1
Fix incorrect PyObject_CallFunction usage (remove extra NULL argument)
hyongtao-code Dec 11, 2025
66fbac7
📜🤖 Added by blurb_it.
blurb-it[bot] Dec 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
📜🤖 Added by blurb_it.
  • Loading branch information
@blurb-it
blurb-it[bot] authored Dec 11, 2025
commit 66fbac7e915b8bb7f37fa318dcbe4b83396d3e44
3 changes: 3 additions & 0 deletions Misc/NEWS.d/next/Library/2025-12-11-23-57-20.gh-issue-142606.Xd3xTx.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Fix two internal C API call sites where ``PyObject_CallFunction`` was
incorrectly passed an extra ``NULL`` argument in
:class:`collections.deque` and in the import machinery. (gh-142606)
Loading