All,
My excuse if this is not the appropriate list for a question essentially concerning the AIX port of Python.
The current port of Python for AIX includes composing an export file (/lib/python2.7/config/python.exp) in which there are a number of functions starting "Py_" or "_Py_".
The Vim package for AIX is built referencing the python.exp file and unfortunately, when functions are removed from libpython, even those which are not called, the vim command detects missing symbols.
The most recent case (May 2017), functions _Py_hgidentity, _Py_hgversion and _Py_svnversion were replaced/removed, see "bpo-27593: Get SCM build info from git instead of hg (#1327)".
Is it correct to assume that the "_Py_" functions are internal (Python name space) that should/must not be called by or made visible to application code ?
Could you indicate a URL to the authoritative API documentation ?
Thanks for your replies.
Mike Wilson
Yes, all symbols starting with _Py are private and must not be used outside CPython internals.
Victor
Le vendredi 27 juillet 2018, WILSON, MICHAEL michael.a.wilson@atos.net a écrit :
All,
My excuse if this is not the appropriate list for a question essentially
concerning the AIX port of Python.
The current port of Python for AIX includes composing an export file
(/lib/python2.7/config/python.exp) in which there are a number of functions starting “Py_” or “_Py_”.
The Vim package for AIX is built referencing the python.exp file and
unfortunately, when functions are removed from libpython, even those which are not called, the vim command detects missing symbols.
The most recent case (May 2017), functions _Py_hgidentity, _Py_hgversion
and _Py_svnversion were replaced/removed, see “bpo-27593: Get SCM build info from git instead of hg (#1327)”.
Is it correct to assume that the “_Py_” functions are internal (Python
name space) that should/must not be called by or made visible to application code ?
Could you indicate a URL to the authoritative API documentation ?
Thanks for your replies.
Mike Wilson
Why would a VIM build refer to the export file for python?
From: Python-Dev python-dev-bounces+robb=datalogics.com@python.org on behalf of "WILSON, MICHAEL" michael.a.wilson@atos.net Date: Friday, July 27, 2018 at 10:27 AM To: "python-dev@python.org" python-dev@python.org Cc: "WILSON, MICHAEL" michael.a.wilson@atos.net Subject: [DLFILTER] [Python-Dev] Exporting Python functions on AIX
All,
My excuse if this is not the appropriate list for a question essentially concerning the AIX port of Python.
The current port of Python for AIX includes composing an export file (/lib/python2.7/config/python.exp) in which there are a number of functions starting “Py_” or “_Py_”.
The Vim package for AIX is built referencing the python.exp file and unfortunately, when functions are removed from libpython, even those which are not called, the vim command detects missing symbols.
The most recent case (May 2017), functions _Py_hgidentity, _Py_hgversion and _Py_svnversion were replaced/removed, see “bpo-27593: Get SCM build info from git instead of hg (#1327)”.
Is it correct to assume that the “_Py_” functions are internal (Python name space) that should/must not be called by or made visible to application code ?
Could you indicate a URL to the authoritative API documentation ?
Thanks for your replies.
Mike Wilson
On 27 July 2018 at 20:23, Rob Boehne robb@datalogics.com wrote:
Why would a VIM build refer to the export file for python?
Because vim includes an optional embedded Python interpreter. Paul
-
Paul Moore -
Rob Boehne -
Victor Stinner -
WILSON, MICHAEL