[ python-Bugs-991883 ] PyObject_CallMethod docs unclear (with dangerous results)

[SourceForge.net]

Bugs item #991883, was opened at 2004-07-15 16:40
Message generated for change (Comment added) made by akuchling
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991883&group_id=5470

Category: Documentation
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Itamar Shtull-Trauring (itamar)
>Assigned to: A.M. Kuchling (akuchling)
Summary: PyObject_CallMethod docs unclear (with dangerous results)

Initial Comment:
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.

----------------------------------------------------------------------

>Comment By: A.M. Kuchling (akuchling)
Date: 2004-08-07 13:54

Message:
Logged In: YES 
user_id=11375

Mentioned in the documentation now; thanks!


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991883&group_id=5470