>> > > 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
Chris McDonough wrote:
>
> > > 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 withou
> > 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 g
Hi!
> It looks like you're leaking requests. This is often the consequence of
> setting an attribute on the REQUEST object which is aquisition wrapped.
> For instance:
>
> REQUEST.adtmldoc = REQUEST['PARENTS'][0]
>
> When requests leak, references to all the objects referenced within the
> re
Hi Christian,
It looks like you're leaking requests. This is often the consequence of
setting an attribute on the REQUEST object which is aquisition wrapped.
For instance:
REQUEST.adtmldoc = REQUEST['PARENTS'][0]
When requests leak, references to all the objects referenced within the
request
