What attic/crypto.py currently does is:
libcrypto = cdll.LoadLibrary(find_library('crypto'))
But there is no guarantee that find_library('crypto') returns a library
that is ABI-compatible with the Python code. For the Debian package, a
quick&dirty fix is to replace the find_library() call with
'libcrypto.so.1.0.0', then hardcode libssl1.0.0 in Depends. But that of
course means that the package would need a sourceful upload by the next
OpenSSL transition.
* Dmitry Shachnev <mity...@gmail.com>, 2014-02-07, 11:37:
a simplier solution will be to use existing modules like python-xattr
and python-crypto, or writing a Python extension where you can use C
code.
Instead of full-blow extension module, you could build a thin C wrapper
over the interesting libcrypto functions, and then dlopen the wrapper
instead of the shared library.
But then I notice that attic already contains some extensions modules
written in Cython, so surely rewritting crypto.py and xattr.py in Cython
shouldn't be a big deal? :-)
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140207111203.ga7...@jwilk.net
