New submission from STINNER Victor <victor.stin...@haypocalc.com>: "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). ---------- components: Interpreter Core files: getarg_oquestion.patch keywords: patch messages: 106624 nosy: haypo priority: normal severity: normal status: open title: PyArg_ParseTuple(): remove old and unused "O?" format versions: Python 2.7, Python 3.2 Added file: http://bugs.python.org/file17478/getarg_oquestion.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8837> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
