On Jan 7, 2008 7:55 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> Fair enough. Just wanted to give some more details as to
> where to look for things that look like leaks, but are in
> fact just results of internal feature of the Python
> interpreter.
We have a hackfest coming up in the Fedora Co
On Jan 4, 2008 11:56 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> > The most common answer I heard was possible fragmentation, meaning
> > there are no or few completely empty blocks to be found. If there are
> > no 'leaks' in the VM, then it's probably related to how memory is
> > freed.
>
> Yo
On Jan 4, 2008 11:10 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> If you're using lots of small objects, you may be running into a
> problem with the Python memory allocation mechanism, pymalloc. It used
> to not return memory to the system. In Python 2.5 (IIRC, could be
> 2.6) this was changed t
On Jan 4, 2008 10:34 AM, Jeroen Ruigrok van der Werven
<[EMAIL PROTECTED]> wrote:
> As various people pointed out to me:
> http://wingolog.org/archives/2007/11/27/reducing-the-footprint-of-python-applications
It did; it's what lead me to Heapy.
> Aside from that (rant), I seriously dislike Python
Hi list,
Firstly, this is my first post here, so I hope I'm not breaking some
unwritten etiquette rule about asking questions involving several
different libraries.
I'm trying to plug some memory leaks in a TurboGears program. We (the
Fedora Project) have a few apps in Turbogears in infrastructu
