[Python-Dev] Python modules should link to libpython
ronaldoussoren at mac.com
Wed Feb 8 19:33:31 CET 2006
On 8-feb-2006, at 16:47, Gustavo J. A. M. Carneiro wrote:
> gjc:/usr/lib/python2.4/lib-dynload$ ldd itertools.so
> libpthread.so.0 => /lib/libpthread.so.0 (0x00002aaaaabcc000)
> libc.so.6 => /lib/libc.so.6 (0x00002aaaaace2000)
> /lib/ld-linux-x86-64.so.2 (0x0000555555554000)
> It seems that Python C extension modules are not linking explicitly to
> libpython. Yet, they explicitly reference symbols defined in
> When libpython is loaded in a global scope all is fine. However, when
> libpython is dlopen()ed with the RTLD_LOCAL flag, python C extensions
> always get undefined symbols.
> This problem happened recently with the nautilus-python package,
> installs an extension for the Nautilus file manager that allows
> extensions in Python. For performance reasons, it now opens
> with RTLD_LOCAL flag, thus breaking python extensions.
> Any thoughts? Should I go ahead and open a bug report (maybe with
> patch), or is this controversial?
I don't know about Linux, but on OSX we don't link with libpython
(or Python.framework) on purpose: this allows you to share extensions
several builds of the same version of Python. If you do link with
and extension that was compiled by a python installed at a different
will result in having two copies of libpython in memory, only one of
is initialized. You end up with very interesting crashes.
> Gustavo J. A. M. Carneiro
> <gjc at inescporto.pt> <gustavo at users.sourceforge.net>
> The universe is always one step beyond logic.
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2157 bytes
Desc: not available
Url : http://mail.python.org/pipermail/python-dev/attachments/20060208/918ae5ee/attachment.bin
More information about the Python-Dev