Change by Tom Birch :
--
components: +C API, Extension Modules
___
Python tracker
<https://bugs.python.org/issue42616>
___
___
Python-bugs-list mailing list
Unsub
Tom Birch added the comment:
Steve Dower: this issue is independent of distutils, reopening
--
components: -Distutils
status: closed -> open
___
Python tracker
<https://bugs.python.org/issu
Tom Birch added the comment:
> Does this affect unix-style builds with --enable-shared or framework builds?
I believe the answer is no, since in both those cases the `python` executable
doesn't contain definitions for any of the libpython symbols. In my testing I
was using a python bin
New submission from Tom Birch :
After https://github.com/python/cpython/pull/12946, there exists an issue on
MacOS due to the two-level namespace for symbol resolution. If a C extension
links against libpython.dylib, all symbols dependencies from the Python C API
will be bound to libpython
