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
PyObject_CallOneArg and PyObject_CallNoArgs should be marked as returning a new reference #113696
Labels
Comments
erlend-aasland
pushed a commit
that referenced
this issue
Jan 4, 2024
… as returning a strong reference (#113697)
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jan 4, 2024
…NoArgs as returning a strong reference (pythonGH-113697) (cherry picked from commit 1ae7ceb) Co-authored-by: Jamie Phan <jamie@ordinarylab.dev>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
Jan 4, 2024
…NoArgs as returning a strong reference (pythonGH-113697) (cherry picked from commit 1ae7ceb) Co-authored-by: Jamie Phan <jamie@ordinarylab.dev>
erlend-aasland
pushed a commit
that referenced
this issue
Jan 5, 2024
erlend-aasland
pushed a commit
that referenced
this issue
Jan 5, 2024
|
Thanks, @ordinary-jamie! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Documentation
PyObject_CallOneArgandPyObject_CallNoArgsshould be updated in the docs with the reference count annotation"Return value: New reference."(as is the case withPyObject_CallFunctionet al.)Linked PRs
The text was updated successfully, but these errors were encountered: