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/2009-May/089710.html below:

[Python-Dev] [unladen-swallow] PEP 384: Defining a Stable ABI

[Python-Dev] [unladen-swallow] PEP 384: Defining a Stable ABI [Python-Dev] [unladen-swallow] PEP 384: Defining a Stable ABIAntoine Pitrou solipsis at pitrou.net
Wed May 20 19:34:42 CEST 2009
Jeffrey Yasskin <jyasskin <at> gmail.com> writes:
> 
> Sorry, I didn't mean to get into a GIL debate. All I'm saying is that
> I don't think changing the definition of Py_INCREF and Py_DECREF
> justifies going to Python 4.0, so I don't think their definitions
> should be part of the ABI. If that's not what the ABI means, that's ok
> too.

Consider, though, that if Py_INCREF and Py_DECREF are not part of the ABI,
enabling the ABI-specific preprocessor symbol will hide them, which might (or
might not!) annoy a lot of extension writers.

(I don't know if there are extensions out there having reference count
increments and decrements in their critical paths)

Regards

Antoine.


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