Antoine Pitrou <pit...@free.fr> added the comment: >From a fresh-compiled Python 2.7:
$ ldd ./python linux-vdso.so.1 => (0x00007fff85cde000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f772f725000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f772f521000) libutil.so.1 => /lib64/libutil.so.1 (0x00007f772f31e000) libm.so.6 => /lib64/libm.so.6 (0x00007f772f09c000) libc.so.6 => /lib64/libc.so.6 (0x00007f772ed2b000) /lib64/ld-linux-x86-64.so.2 (0x00007f772f941000) (same with 3.3) This is therefore a problem with the Debian package, not with the vanilla Python build (when using default options). Also, the reason ssl is imported when socket is imported in Python 2 is for compatibility reasons. It doesn't happen in Python 3: $ grep ssl Lib/socket.py $ ldd build/lib.linux-x86_64-3.3-pydebug/_socket.cpython-33dm.so linux-vdso.so.1 => (0x00007fffa2f21000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f227ff8f000) libc.so.6 => /lib64/libc.so.6 (0x00007f227fc1e000) /lib64/ld-linux-x86-64.so.2 (0x00007f22803e1000) Therefore, closing as not a Python bug. > Is the Python dev team too fast for reality? ;-) Actually, releasing a new version every 18 months (not counting bugfix releases) makes us fairly conservative (perhaps too much) in the modern software ecosystem ;) ---------- nosy: +pitrou resolution: -> works for me status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13580> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com