[Python-Dev] Python 3.7: remove all private C functions from the Python C API? (original) (raw)

Yury Selivanov yselivanov.ml at gmail.com
Mon Sep 12 12:52:42 EDT 2016

Some of the functions we have are really intended to be used only by the interpreter itself. For those it would be cool to have them in private headers (AFAIK we already do this, see dict-common.h for instance). Other than that, I think that using the underscore convention is fine.

Yury

On 2016-09-11 4:37 AM, Victor Stinner wrote:

Hi,

Currently, Python has 3 C API: * python core API * regular API: subset of the core API * stable API (ABI?), the PyLIMITEDAPI thing: subset of the regular API For practical purpose, all functions are declared in Include/*.h. Basically, Python exposes "everything". There are private functions which are exported using PyAPIFUNC(), whereas they should only be used inside Python "core". Technically, I'm not sure that we can get ride of PyAPIFUNC() because the stdlib also has extensions which use a few private functions. For Python 3.7, I propose that we move all these private functions in separated header files, maybe Include/private/ or Include/core/, and not export them as part of the "regular API". The risk is that too many C extensions rely on all these tiny "private" functions. Maybe for performance. I don't know. What do you think? See also the issue #26900, "Exclude the private API from the stable API": http://bugs.python.org/issue26900 Victor

Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/yselivanov.ml%40gmail.com

More information about the Python-Dev mailing list