"BAW" == Barry A Warsaw email@example.com writes:
"FL" == Fredrik Lundh firstname.lastname@example.org writes:
FL> while 1: compile("print 'hello'\n", "<string>", "exec")
FL> current CVS leaks just over 1k per call to compile. FL> 1.5.2 and 2.0 doesn't leak a byte.
FL> make the script a little more complex, and it leaks even more FL> (4k for a small function, 650k for Tkinter.py, etc).
BAW> I have plans to spend a fair bit of time running memory/leak BAW> analysis over Python after the conference. I'm kind of waiting BAW> until we enter beta, i.e. feature freeze.
It would be helpful to get some analysis on this known problem before the beta release.