[Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Mon Mar 21 13:38:32 CET 2011
- Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
- Next message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 21 Mar 2011 04:09:35 +0100 "Martin v. Löwis" <martin at v.loewis.de> wrote:
Since Python 2.5, we maintain two versions of PyArgParseTuple: one outputting int; the other one outputting Pyssizet.
The former should have been removed in 3.0, but this was forgotten. Still, I would like people to move over to the new version, so that extension modules will typically support 64-bit collections well. Therefore, I'd like to propose that the int version is deprecated in 3.3.
+1 !
Given the recent discussion about backwards compatibility: what's the best approach? What warning should be emitted, if any? (the warning would only be generated if an s# or similar format was actually encountered - not just if merely PyArgParseTuple is called).
I'd say a DeprecationWarning. They are quiet by default anyway...
Regards
Antoine.
- Previous message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
- Next message: [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]