[ python-Bugs-991883 ] PyObject_CallMethod docs unclear (with
dangerous results)
SourceForge.net
noreply at sourceforge.net
Thu Jul 15 22:40:27 CEST 2004
Bugs item #991883, was opened at 2004-07-15 16:40
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991883&group_id=5470
Category: Documentation
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Itamar Shtull-Trauring (itamar)
Assigned to: Nobody/Anonymous (nobody)
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.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=991883&group_id=5470
More information about the Python-bugs-list
mailing list