Jakub Wilk <jw...@debian.org> writes: > Public Python extension modules, i.e. *.so files in one of these > directories:
> /usr/lib/pyshared/pythonX.Y/ > /usr/lib/python-support/PACKAGENAME/pythonX.Y/ > /usr/lib/pythonX.Y/site-packages/ > /usr/lib/pythonX.Y/dist-packages/ > should not be linked to libpythonX.Y. Such linkage is not necessary for > a module to work correctly and it causes dpkg-shlibdeps to generate > dependencies that are too strict. See e.g. bugs #472314, #445411, > #445423, #470290. Not linking the add-on modules with libpython is going to cause you other problems with applications that embed Python via a dynamic loader interface. We know this from experience with Perl. This therefore makes me very nervous, since you will run into problems with this approach to dynamic linking. vorlon also points out that, in the current scheme, if you get libpython2.5 and libpython2.6 loaded at the same time somehow, you end up with a mess. I realize that this is the way that Python has been doing it for a while, and I'm not rejecting the request, but I think this may not be the correct technical approach inside Python. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
