Reid Kleckner wrote:
> 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.

Even if you don't, it will *still* be shared, since the operating system
will also share executables.

Regards,
Martin
_______________________________________________
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

Reply via email to