Message106624
"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). |
|
Date |
User |
Action |
Args |
2010-05-27 22:59:41 | vstinner | set | recipients:
+ vstinner |
2010-05-27 22:59:41 | vstinner | set | messageid: <1275001181.3.0.513228371252.issue8837@psf.upfronthosting.co.za> |
2010-05-27 22:59:39 | vstinner | link | issue8837 messages |
2010-05-27 22:59:38 | vstinner | create | |
|