Hi all,
The ExtFile product I maintain keeps its payload on the filesystem.
All operations are performed using temporary files which are then
saved or deleted on transaction commit or abort respectively.
To this end an ExtFile provides _finish and _abort methods which are
hooked up to a
El jue, 23-03-2006 a las 15:02 -0500, Tim Peters escribió:
[Antonio Beamud Montero]
But my server doesn't free any memory, now it uses 55Mb of resident
size... How I can debug this references?
Many layers are involved in memory management, from ZODB through
Python down to your platform
Stefan H. Holek schrieb:
Hi all,
The ExtFile product I maintain keeps its payload on the filesystem. All
operations are performed using temporary files which are then saved or
deleted on transaction commit or abort respectively.
Do you remember, when you use the tempfile module, you get
On Mar 24, 2006, at 9:11 AM, Chris Withers wrote:
Hi All,
What happens if you call _p_deactivate() on a modified object but
before the modifications have been committed?
Do the modifications get lost or will they still be saved when the
next commit happens after the _p_deactivate()?
[Chris Withers]
Anyone ever see this error before and have a clue what it means?
File lib/python/Zope2/Startup/__init__.py, line 47, in startup
starter.setConfiguration(cfg)
File lib/python/Zope2/App/startup.py, line 100, in startup
File
Antonio Beamud Montero wrote at 2006-3-23 09:26 +0100:
...
But my server doesn't free any memory, now it uses 55Mb of resident
size... How I can debug this references?
It has no chance -- and this is neither the fault of Python nor
of the ZODB but of C's standard memory management:
C does
