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.
Created on 2010年05月27日 22:59 by vstinner, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| 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). |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:01 | admin | set | github: 53083 |
| 2010年05月28日 21:55:57 | vstinner | set | status: open -> closed resolution: fixed messages: + msg106692 |
| 2010年05月27日 23:02:51 | vstinner | set | versions: - Python 2.7 |
| 2010年05月27日 23:00:07 | vstinner | set | nosy:
+ mark.dickinson |
| 2010年05月27日 22:59:39 | vstinner | create | |