➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: PyObject_CallMethod docs unclear (with dangerous results)
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: akuchling Nosy List: akuchling, itamar
Priority: normal Keywords:

Created on 2004-07-15 20:40 by itamar, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg21639 - (view) Author: Itamar Shtull-Trauring (itamar) Date: 2004-07-15 20:40 
PyObject_CallMethod doesn't make clear that passing a
tuple of args is the correct way to use it. While it
does work when you don't pass a tuple, this causes
memory leak - the objects passed in get extra incref,
AFAICT, so it's worth emphasizing the correct API.
msg21640 - (view) Author: A.M. Kuchling (akuchling) * (Python committer) Date: 2004-08-07 17:54 
Logged In: YES 
user_id=11375

Mentioned in the documentation now; thanks!
History
Date User Action Args
2022-04-11 14:56:05adminsetgithub: 40576
2004-07-15 20:40:25itamarcreate