On 8/1/07, Adam Kalsey <[EMAIL PROTECTED]> wrote: > > Are there any profiling tools for Python that would be useful in finding > the section of code that's a likely culprit?
http://www.google.com/search?q=python+memory+profiler returned two likely candidates: - http://pysizer.8325.org/ - http://guppy-pe.sourceforge.net/#Heapy -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
_______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports