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/2017-March/147644.html below:

[Python-Dev] Py_SIZE vs PyXXX_GET_SIZE

[Python-Dev] Py_SIZE vs PyXXX_GET_SIZEBenjamin Peterson benjamin at python.org
Tue Mar 21 02:22:46 EDT 2017
On Mon, Mar 20, 2017, at 13:18, Antoine Pitrou wrote:
> On Mon, 20 Mar 2017 13:26:34 +0200
> Serhiy Storchaka <storchaka at gmail.com> wrote:
> > What is the preferable way of getting the size of tuple, list, bytes, 
> > bytearray: Py_SIZE or PyTuple_GET_SIZE, PyList_GET_SIZE, 
> > PyBytes_GET_SIZE, PyByteArray_GET_SIZE? Are macros for concrete types 
> > more preferable or they are outdated?
> 
> +1 for using concrete macros.  Py_SIZE is a low-level internal thing
> (e.g. it will return a negative size on negative ints).

+1 Py_SIZE is an implementation detail of varsize types. Using the
concrete macros also the implementation to change without altering API
consumers.
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