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.

Title: PyArg_ParseTuple(): remove old and unused "O?" format
Type: Stage:
Components: Interpreter Core Versions: Python 3.2
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: mark.dickinson, vstinner
Priority: normal Keywords: patch

Created on 2010-05-27 22:59 by vstinner, last changed 2022-04-11 14:57 by admin. This issue is now closed.

File name Uploaded Description Edit
getarg_oquestion.patch vstinner, 2010-05-27 22:59
Messages (2)
msg106624 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2010-05-27 22:59
"O?" format was introduced by r4301 (15 years, 9 months ago). PyArg_ParseTuple() was first documented in Python 2.2, but without the full list of all formats. The format list was added to Python 2.3, but "O?" was never documented. So I get that no third party progam use it.

In Python trunk, "O?" is no more used and so I propose to remove it to simplify getarg.c (simplify getarg cannot be a bad thing). PyArg_ParseTuple() has now better formats than "O?".


"O&" calls a callback: if the callback returns 0, raise an error; otherwise gets the object. Example of callbacks: PyXXX_Check() function (eg. PyInt_Check()).


The full Python test suite pass without any error on a patched Python (trunk).
msg106692 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2010-05-28 21:55
Commited: r81588 (py3k), blocked in 3.1 (r81589).
Date User Action Args
2022-04-11 14:57:01adminsetgithub: 53083
2010-05-28 21:55:57vstinnersetstatus: open -> closed
resolution: fixed
messages: + msg106692
2010-05-27 23:02:51vstinnersetversions: - Python 2.7
2010-05-27 23:00:07vstinnersetnosy: + mark.dickinson
2010-05-27 22:59:39vstinnercreate