This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients docs@python, serhiy.storchaka, vstinner
Date 2016-12-15.08:36:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481790961.1.0.0700086912401.issue28977@psf.upfronthosting.co.za>
In-reply-to
Content
The PyObject_CallFunction() function has a special case if the format string is "O". See my email thread on python-dev:
https://mail.python.org/pipermail/python-dev/2016-December/146919.html

Serhiy wrote: "It is documented for Py_BuildValue(), and the documentation of PyObject_CallFunction() refers to Py_BuildValue()." which is true, but I would prefer to be more explicit to avoid bad surprises (see issues #21209 and #28920).

Attached patch modifies PyObject_CallFunction() doc to mention the "O" format special case in the .rst doc and the .h comment.

The documentation of PyObject_CallMethod() and _PyObject_CallMethodId() should also be modified, but I would prefer to wait for a first review on the added text before modifying all functions.

I proposed to only modify Python 3.7 because Include/abstract.h was a in a bad shape: I rewrote this file to make it easier to maintain, but only in Python 3.7, see issue #28838.
History
Date User Action Args
2016-12-15 08:36:01vstinnersetrecipients: + vstinner, docs@python, serhiy.storchaka
2016-12-15 08:36:01vstinnersetmessageid: <1481790961.1.0.0700086912401.issue28977@psf.upfronthosting.co.za>
2016-12-15 08:36:01vstinnerlinkissue28977 messages
2016-12-15 08:36:00vstinnercreate