* Scott Kitterman: > I did miss that, but Python only maintains ABI per python version, so you > need > a separate .so for python3.2 and 3.3 to support both. So something is wrong > in that that one .so can't support both 3.2 and 3.3. You'll see that with my > patch, dh_python3 does act on the .so and generate correct dependencies. > It's > now: > > usr/lib/python3/dist-packages/libhivexmod.cpython-32mu.so
Mhm. I wonder why it doesn't do that if python2 and python3 bindings are in the same binary package. > In python3 there is version specific ABI tagging in the .so name so that .so > files for multiple versions can be installed in the same directory. This is > described in http://www.python.org/dev/peps/pep-3149/ . Thanks you for the pointer. After some experimentation, I have found a way to get autoconf/automake/libtool to recognize that special extension and build the right files. Also thank you for explainting the rationale behind python3-foo packages. Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
