On Oct 2, 4:47 pm, Andrew MacIntyre
wrote:
> There are two things you need to be aware of in this situation:
>
> - not all Python's memory is allocated through Python's specialised
> malloc() - int and float objects in particular (in 2.x at least) are
> allocated directly via a privately man
Matt Ernst wrote:
{...}
I thought Evan Jones altered Python to deal with this very problem,
and the change went into the release of 2.5.
Here is Tim Peters announcing the change:
http://mail.python.org/pipermail/python-dev/2006-March/061991.html
He included this simple test program to show th
My apologies in advance if this has been addressed before. Google does
not presently seem to return search results for this group from more
than a couple of months ago.
I have some long-running Python processes that slowly increase in
resident memory size, and whose resident size goes down only wh
