[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-12 Thread kxroberto
kxroberto kxrobe...@users.sourceforge.net added the comment: (I often wonder why software today isn't much faster than years ago - though the nominal speed of hardware increases tremendously. package sizes grow, without appropriate growth of functionality. This is one example how the

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Overall I wonder why you post here on the main topic resource usage, when you don't care about issues of magnitude 2x memory usage. Because you are talking about a fixed overhead of a mere 2MB (IIUC), which is moreover shared between all

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-12 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: I just checked the file python2.6_2.6.6-8.diff.gz from the Debian python2.6 package: http://packages.debian.org/squeeze/python2.6 This diff file contains a patch to build _hashlib and _ssl extensions statically that modifies

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread kxroberto
New submission from kxroberto kxrobe...@users.sourceforge.net: With transition from Python2.5 to Python2.6 on current Debian stable I noticed that the python2.6 executable has now 2x size of python2.5's. Half of lib-dynload/* obviously have been embedded into the executable by default. While

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread maniram maniram
maniram maniram maniandra...@gmail.com added the comment: +1 -- nosy: +maniram.maniram ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13580 ___ ___

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread Jesús Cea Avión
Jesús Cea Avión j...@jcea.es added the comment: I see this effect in the stock ubuntu 10.04 python 2.6. I can't see it in my selfcompiled binaries for Solaris 10 and 2.7 ubuntu. The reason seems to be that my compilated code uses the python shared libs, while the stock Ubuntu 10.04 python 2.6

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread R. David Murray
R. David Murray rdmur...@bitdance.com added the comment: So isn't this saying that this is a problem with the distribution packaging and not with CPython itself? -- nosy: +barry, r.david.murray ___ Python tracker rep...@bugs.python.org

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread kxroberto
kxroberto kxrobe...@users.sourceforge.net added the comment: Of course, as soon as we use sockets, we will bring SSL in Indeed, as it is now. Suggestions: * urllib.URLOpener.open_https shall always exist, but fail on runtime. non-existance with strange AttributeError is inelegant..bogus.

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread kxroberto
kxroberto kxrobe...@users.sourceforge.net added the comment: Can you try to compile python using the shared lib yes I can try lot of things, but I'd need to do this on many machines. Yet I didn't create this issue for some local purpose ;-) 99% of Pythons are installed by apt-get, .msi etc.

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: From a fresh-compiled Python 2.7: $ ldd ./python linux-vdso.so.1 = (0x7fff85cde000) libpthread.so.0 = /lib64/libpthread.so.0 (0x7f772f725000) libdl.so.2 = /lib64/libdl.so.2 (0x7f772f521000)

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread kxroberto
kxroberto kxrobe...@users.sourceforge.net added the comment: It doesn't happen in Python 3 Yet the cheap/unnecessary pre-imports of ssl in those other mentioned socket using libs (urllib (cgi!),httplib,smtplib,pop,imap...) exist there. socket is rarely used directly, so not much difference to

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: It doesn't happen in Python 3 Yet the cheap/unnecessary pre-imports of ssl in those other mentioned socket using libs (urllib (cgi!),httplib,smtplib,pop,imap...) exist there. socket is rarely used directly, so not much difference to Py2 in

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread kxroberto
kxroberto kxrobe...@users.sourceforge.net added the comment: It doesn't happen in Python 3 Yet the cheap/unnecessary pre-imports of ssl in those other mentioned socket using libs (urllib (cgi!),httplib,smtplib,pop,imap...) exist there. socket is rarely used directly, so not much difference

[issue13580] Pre-linkage of CPython =2.6 binary on Linux too fat (libssl, libcrypto)

2011-12-11 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: (I often wonder why software today isn't much faster than years ago - though the nominal speed of hardware increases tremendously. package sizes grow, without appropriate growth of functionality. This is one example how the rescources are