Andrea Griffini a écrit : > Bruno Desthuilliers wrote: > > >> ... and on > >>> the opposite I didn't expect that fighting with object >>> leaking in complex python applications was that difficult >>> (I've heard of zope applications that just gave up and >>> resorted to the "reboot every now and then" solution). >>> >> Zope is a special case here, since it relies on an object database... > > > Just to clarify my post... I found by being punched myself > in the nose what does it mean to have a complex python > application that suffers from object leaking; it's not > something I only read about zope programs. > > But why zope applications would be a special case ?
1/ because of how Zope and the ZODB work 2/ because Zope is an unusually complex Python application. FWIW, I've never had any memory problem with other Python applications and/or frameworks I've used so far (ie: in the past seven years) - most of them being somewhat 'simpler' than if they had been implemented in C or C++... -- http://mail.python.org/mailman/listinfo/python-list
