[Zope-dev] disabling gc does not necessarily hide memory corruption
Chris McDonough
chrism@zope.com
Tue, 18 Dec 2001 08:43:11 -0500
It is no longer based on bytecodehacks, it uses Jeremy's compiler
module. It did produce some (unintended) circrefs, but I think the
version in CVS as well as the version that will ship with Python 2.2 has
these taken out.
Toby Dickenson wrote:
> On Mon, 17 Dec 2001 23:13:54 -0500, Chris McDonough <chrism@zope.com>
> wrote:
>
>
>>Ah ok... yeah, there were reportedly several leaks in the compiler stuff
>>that have been fixed in CVS. I imagine that's what this is.
>>
>
> Is the compiler still based on bytecodehacks? If so, I dont think this
> is a bug
>
> As I understand it, that package is designed to leave cyclic garbage
> around under the assumption that python's garbage collector will break
> the cycles. Early versions of bytecodehacks broke the cycles manually,
> at a great performance cost.
>
>
> Toby Dickenson
> tdickenson@geminidataloggers.com
>
> _______________________________________________
> Zope-Dev maillist - Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope )
>
--
Chris McDonough Zope Corporation
http://www.zope.org http://www.zope.com
"Killing hundreds of birds with thousands of stones"