On Jan 10, 2008, at 8:58 PM, Chris McDonough wrote:
Hi folks,
Your note today pointing at code I wrote made me pay closer
attention. :)
While messing with Zope2's webdav implementation, I ran across this
bit of memory-management code:
dflag = hasattr(ob, '_p_changed') and
Summary of messages to the zope-tests list.
Period Thu Jan 10 12:00:00 2008 UTC to Fri Jan 11 12:00:00 2008 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Test failures
-
Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux
From: Zope Unit Tests
Date: Thu Jan 10
Hi,
I was trying to read and understand zope.release and zope.kgs (to be able to add
zope.app.locales 3.4.1 into the upcoming zope 3.4).
So I've tried to run all the tests of the KGS :
-
$ ./bin/test -vpc1
Running tests at level 1
On Jan 11, 2008, at 9:24 AM, Jim Fulton wrote:
While messing with Zope2's webdav implementation, I ran across this
bit of memory-management code:
dflag = hasattr(ob, '_p_changed') and (ob._p_changed == None)
... stuff ...
if dflag:
ob._p_deactivate()
I actually think this should
I'm trying to figure out where (in the svn) the following file is:
http://download.zope.org/zope3.4/controlled-packages.cfg
Isn't it supposed to be the same as the one found in zope.release (trunk or
3.4.0b2 tag) ?
Where does the difference come from?
Christophe
On Jan 11, 2008, at 1:08 PM, Chris McDonough wrote:
...
Related but fuzzier... is it your expectation that the amount
of memory used for a database walk routine that tries to do memory
management via some combination of connection.cacheMinimize-or-
cacheGC() every-n-iterations (no calls
