➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients BreamoreBoy, ethan.furman, larry, lemburg, mark.dickinson, pitrou, rhettinger, scoder, serhiy.storchaka
Date 2015-05-11.11:05:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <55508CE5.3070007@egenix.com>
In-reply-to <1431337341.22.0.889973395013.issue24138@psf.upfronthosting.co.za>
Content 
On 11.05.2015 11:42, Serhiy Storchaka wrote:
> 
> Pre-allocating a block has a disadvantage. It is hard to free allocated block. The program can create a lot of integers, then drop most of them, and request the memory for other needs, but blocks once allocated for integers would not freed. This is not trivial design decision and should be discussed on Python-Dev and accepted by BDFL.

True, but if it's only 1-4k RAM, I don't think anyone would mind :-)

Python 2 is doing exactly that with 1k RAM for the integer free
list. I think it was one of the first free lists ever added to
Python, so done in a time when RAM was expensive ;-).
History
Date User Action Args
2015-05-11 11:05:13lemburgsetrecipients: + lemburg, rhettinger, mark.dickinson, pitrou, scoder, larry, BreamoreBoy, ethan.furman, serhiy.storchaka
2015-05-11 11:05:13lemburglinkissue24138 messages
2015-05-11 11:05:13lemburgcreate