Alexander Belopolsky <[EMAIL PROTECTED]> added the comment: Placing the entire library tree in /usr/lib64 is wasteful on dual 32/64bit installation, but placing just the C modules there is contrary to python import logic and may cause problems to relative imports.
I have suggested what I believed was a workable solution: have 64-bit python search lib64-dynload subdirectories instead of lib-dynload. See http://mail.python.org/pipermail/python-dev/2007-April/072653.html Currently $(prefix)/pythonX.Y/lib-dynload is inserted in the sys.path, but I think it would be better to handle this inside the importer in a way similar to how the importer looks for both foo.so and foomodule.so when importing foo. This would allow submodules and user modules treated the same way. _____________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1294959> _____________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
