summaryrefslogtreecommitdiff
path: root/Doc/faq
diff options
context:
space:
mode:
authorSerhiy Storchaka <storchaka@gmail.com>2015-06-21 17:11:21 +0300
committerSerhiy Storchaka <storchaka@gmail.com>2015-06-21 17:11:21 +0300
commit03863d2b290d0856d7647a0275a73b55b6589fa7 (patch)
treeb108c989aeb591eb444722e7f0046c75689182ab /Doc/faq
parent5fa22fc088ac44c5652107c7c17cda01eaa84a28 (diff)
downloadcpython-git-03863d2b290d0856d7647a0275a73b55b6589fa7.tar.gz
Fixed documentation of functions with const char* arguments.
Diffstat (limited to 'Doc/faq')
-rw-r--r--Doc/faq/extending.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/faq/extending.rst b/Doc/faq/extending.rst
index 02bba591cf..fea5a57601 100644
--- a/Doc/faq/extending.rst
+++ b/Doc/faq/extending.rst
@@ -115,8 +115,8 @@ call, a format string like that used with :c:func:`Py_BuildValue`, and the
argument values::
PyObject *
- PyObject_CallMethod(PyObject *object, char *method_name,
- char *arg_format, ...);
+ PyObject_CallMethod(PyObject *object, const char *method_name,
+ const char *arg_format, ...);
This works for any object that has methods -- whether built-in or user-defined.
You are responsible for eventually :c:func:`Py_DECREF`\ 'ing the return value.