Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!newsfeed.tele2net.at!news.panservice.it!feed.xsnews.nl!border01.ams.xsnews.nl!feeder04.ams.xsnews.nl!feeder03.ams.xsnews.nl!abp001.ams.xsnews.nl!frontend-F09-06.ams.news.kpn.nl
From: Cecil Westerhof <Cecil@decebal.nl>
Newsgroups: comp.lang.python
Subject: Re: l = range(int(1E9))
Organization: Decebal Computing
References: <87k2wtvbx1.fsf@Equus.decebal.nl> <mailman.135.1430413555.3680.python-list@python.org> <mhtnpg$fsf$1@dont-email.me> <87mw1ptpr0.fsf@Equus.decebal.nl> <mailman.146.1430427228.3680.python-list@python.org> <mhu6df$6bs$2@dont-email.me> <CAPTjJmrs=a=L9TiRUnBPs561bEQFsoBv+3oaQmez5Yi-1gEW6A@mail.gmail.com> <mailman.152.1430435562.3680.python-list@python.org> <87383gsxbd.fsf@Equus.decebal.nl> <3374990.nA8q5WTVfI@PointedEars.de>
X-Face: "(y8cC@tg_12{">GF'UXTW]FHI2wMiZNrnf'1EFQ&O#$m:f#O7+7}kR<J%a^F2lh4[N~Yz4 nSp#c+aQo1b5=?HcNEkQ7QzF<])O3X4MDL/AYjys&*mt>,v+Pti8=Vi/Z"g^?b"E
X-Homepage: http://www.decebal.nl/
Date: Fri, 01 May 2015 14:22:51 +0200
Message-ID: <87vbgco5b8.fsf@Equus.decebal.nl>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:fwQA6Ulw3OYRvdP5+Q89cK3J0SU=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Lines: 34
NNTP-Posting-Host: 81.207.62.244
X-Trace: 1430483330 news.kpn.nl 20459 81.207.62.244@kpn/81.207.62.244:46910
Xref: csiph.com comp.lang.python:89730

Op Friday 1 May 2015 13:15 CEST schreef Thomas Lahn:

> Cecil Westerhof wrote:
>
>> By the way: I also see python3.4 and python3.4m. Any idea where the
>> m stands for?
>
> I googled for “python3.4m” and found as second result

Eh, I could/should have done that myself. :-(
Nice that you do not burn me. :-D


> <http://stackoverflow.com/questions/16675865/difference-between-python3-and-python3m-executibles>
>
> In a nutshell: python3.4m was built with configure option
> “--with-pymalloc” which causes the resulting implementation to use
> “Pymalloc, a specialized object allocator written by Vladimir
> Marangozov, […] a feature added to Python 2.1. Pymalloc is intended
> to be faster than the system malloc() and to have less memory
> overhead for allocation patterns typical of Python programs. The
> allocator uses C's malloc() function to get large pools of memory
> and then fulfills smaller memory requests from these pools.”
>
> See also: <https://github.com/Homebrew/homebrew/issues/32402> (first
> result)

Something to look in later. Looks interesting, but have a ‘few’ things
that are more important.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof