A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109667.html below:

[Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple

[Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTuple [Python-Dev] Deprecating non-Py_ssize_t use of PyArg_ParseTupleVictor Stinner victor.stinner at haypocalc.com
Mon Mar 21 15:21:13 CET 2011
Le lundi 21 mars 2011 à 04:09 +0100, "Martin v. Löwis" a écrit :
> Since Python 2.5, we maintain two versions of PyArg_ParseTuple:
> one outputting int; the other one outputting Py_ssize_t.
> 
> 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.

By the way, what is the status of migration to Py_ssize_t of CPython
extensions? I suppose that adding a warning will quickly give an answer.

Victor

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4