On Thu, Jan 21, 2010 at 7:25 AM, Antoine Pitrou <solip...@pitrou.net> wrote: >> 32-bit; gcc 4.0.3 >> >> +-------------+---------------+---------------+----------------------+ | >> Binary size | CPython 2.6.4 | CPython 3.1.1 | Unladen Swallow r988 | >> +=============+===============+===============+======================+ | >> Release | 3.8M | 4.0M | 74M | >> +-------------+---------------+---------------+----------------------+ | > > This is positively humongous. Is there any way to shrink these numbers > dramatically (I'm talking about the release builds)? Large executables or > libraries may make people anxious about the interpreter's memory > efficiency; and they will be a nuisance in many situations (think making > standalone app bundles using py2exe or py2app).
When we link against LLVM as a shared library, LLVM will still all be loaded into memory, but it will be shared between all python processes. The size increase is a recent regression, and we used to be down somewhere in the 20 MB range: http://code.google.com/p/unladen-swallow/issues/detail?id=118 Reid _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
