[New-bugs-announce] [issue17095] Modules/Setup *shared* support broken

Thomas Wouters report at bugs.python.org
Thu Jan 31 22:54:56 CET 2013

New submission from Thomas Wouters:

At some point (probably in 3.2) the support for shared modules built using Modules/Setup was broken, for two reasons:

 - Python no longer considers 'foomodule.so' when looking for a module called 'foo', but Modules/makesetup still appends 'module.so' for a 'foo' module.

 - Python no longer considers Modules/ to be the exec_prefix (and instead uses what was loaded from the build-info .txt written by setup.py) but the build process still leaves these Modules/Setup-built shared modules in the Modules directory (and it doesn't know about the directory setup.py will make, so it can't really do anything else.)

This patch fixes both problems, by making Modules/makesetup name shared library modules 'foo.so' and by adding the Modules subdirectory to sys.path (after the setup.py-provided directory) when running from the build directory. (The existing build process has no problem _installing_ the Modules/Setup-built extension modules, it's just Python that doesn't know how to find them.)

components: Build
files: getpath.diff
keywords: patch
messages: 181048
nosy: twouters
priority: normal
severity: normal
status: open
title: Modules/Setup *shared* support broken
versions: Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file28928/getpath.diff

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list