[Python-Dev] PyEval_Call* convenience functions

Georg Brandl g.brandl at gmx.net
Fri Apr 24 20:59:01 CEST 2009

Tim Lesher schrieb:
> Is there a reason that the PyEval_CallFunction() and
> PyEval_CallMethod() convenience functions remain undocumented? (i.e.,
> would a doc-and-test patch to correct this be rejected?)
> I didn't see any mention of this coming up in python-dev before.
> Also, despite its name, PyEval_CallMethod() is quite useful for
> calling module-level functions or classes (given that it's just a
> PyObject_GetAttrString plus the implementation of
> PyEval_CallFunction).  Is there any reason (beyond its undocumented
> status) to believe this use case would ever be deprecated?

FWIW, there's also PyObject_CallMethod(); all PyObject_Call* variants are
documented, but none of the PyEval_Call* functions are.  I actually don't
know why we have two sets of these, with partially conflicting definitions;
perhaps someone else can shed some light?


Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list