[Zope-dev] memory eating Zope..

[Toby Dickenson]

>> > > Note that this is likely caused by some sort of brainbending =
circular
>> > > reference problem that might be helped by Python 2.X's cyclic =
garbage
>> > > collector.
>> >
>> > Well, will also try out python 2.x then... (btw. are all 2.x python =
versions
>> > working without problems with Zope? Don't want to get a new problem =
when
>> > resolving the old one ;-)
>>=20
>> Sort of in a bad state at the moment.  2.4 requires Python 2.1, but =
it's
>> in alpha.  2.3.2 isn't guaranteed to work with Python 2.X.  So you're
>> sort of screwed if you want support.  OTOH, 2.3.2 is reported to work
>> fine with Python 2.X, although if you post Python release-related
>> weirdnesses here with 2.3.2, they'll likely be ignored in favor of
>> directing you to 2.4 when it's out.
>
>We're currently using python 2.1 to run zope 2.3.2 with no ill effects. =
We
>have written our own product that uses some OFS stuff, Catalog and ZPT. =
Not
>much else...

The most serious problem with Zope 2.3.x on Python 2.0 that I have
discovered so far is that Zope's xml-formatted export doesnt handle
unicode objects. If you find anything that doesnt work, it will have
to be fixed for Zope 2.4, and it shouldnt be too hard to back-port
that fix into 2.3.x.

Having said that, Python's garbage collector *needs* support from
container objects. Acquisition wrappers dont implement this support
(yet), and therefore I suspect a Python upgrade will not help you with
this memory leak problem.

Toby Dickenson
tdickenson@geminidataloggers.com