On 3/7/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: > Hrm: http://evanjones.ca/python-memory.html I remember reading that article before :-)
> I was fairly annoyed to run python from the command line and: > blar="hi" > saw memory usage go up a tad > del blar > memory usage never returned true, but I think if you allocate another string it won't go back up. You'd have to stick something in a loop before you see decent results. -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Tue Mar 7 00:54:37 2006 From: [EMAIL PROTECTED] (Daniel Henninger) Date: Tue Mar 7 00:54:45 2006 Subject: [py-transports] PyICQ-t installed :) In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> > On 3/7/06, Daniel Henninger <[EMAIL PROTECTED]> wrote: >> Hrm: http://evanjones.ca/python-memory.html > I remember reading that article before :-) On a bright note, I checked out the sourceforge repository that includes the guy's patch and as of feb of this year, looks like there's going to be much better memory handling soon-ish! Maybe 2.5? >> I was fairly annoyed to run python from the command line and: >> blar="hi" >> saw memory usage go up a tad >> del blar >> memory usage never returned > true, but I think if you allocate another string it won't go back up. > You'd have to stick something in a loop before you see decent results. Yeah, I see what you mean. I'm not entirely sure how I'm supposed to know what's causing memory leaks though. =( I don't even know that there -are- any based off this. Any ideas y'all? (I'm still releasing a new version in a bit here of both transports) Daniel
