Some functions in cpython are private. These APIs
are called from only python executable or DLL.
They are not called even from extension modules in stdlib.
In this time, I want to keep _PyObject_GetMethod private.
As far as I know, it is used to expose the function from DLL user on Windows.
So I think when the private function is not intended to be
called from outside of DLL, it should not use PyAPI_FUNC.
Am I collect?
Currently, many private APIs uses `PyAPI_FUNC()`.
Is there any downside about having much unnecessary exported functions?
(e.g. slower calling invention is used, bothering link time
optimization, LoadLibrary get slower, etc...)
Inada Naoki <songofacandy(a)gmail.com>
Hey Python developers,
I just published the initial release of PyOxidizer - a utility for
producing self-contained, potentially single file executable Python
applications. You can read more about it at
I wanted to draw this list's attention to it because I think PyOxidizer
could have significant implications for the Python community. And the 2nd
to final section in the blog post is of particular relevance to CPython's
I want to state explicitly that I would prefer to work with the Python
community in whatever appropriate capacity is needed to advance the state
of Python application distribution. (I have already participated in
discussions about PEP 587.) PyOxidizer is still young and there's a long
way to go. But I would love to e.g. implement PyOxidizer with an eye
towards incorporation in official Python packaging tools a few years down
the road. I'm not too familiar with the various day-to-day happenings of
Python and Python Packaging. But if you steer me in the right direction, I
could start getting involved...
I hope you like PyOxidizer!