[Python-Dev] PyEval_Call* convenience functions (original) (raw)
Tim Lesher tlesher at gmail.com
Fri Apr 24 19:44:13 CEST 2009
- Previous message: [Python-Dev] Dates in python-dev
- Next message: [Python-Dev] PyEval_Call* convenience functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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?
Thanks.
-- Tim Lesher <tlesher at gmail.com>
- Previous message: [Python-Dev] Dates in python-dev
- Next message: [Python-Dev] PyEval_Call* convenience functions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]