[Zope-dev] disabling gc does not necessarily hide memorycorruption

[Chris McDonough]

I just found out that the RestrictedPython package isn't actually yet fixed!
Shane is working on it.  He's sweating and I think I almost heard him curse
once. ;-)  So please hang tight and we'll let you know when it's safe to go
in the water.

Note that at the time that it's fixed, all that needs to be done is to
download the tarball as per Martijn's instructions, move the current
"RestrictedPython" package aside, and put the new RestrictedPython package
in its place, restart Zope.

----- Original Message -----
From: "Leonardo Rochael Almeida" <leo@hiper.com.br>
To: "Zope Developers list" <zope-dev@zope.org>
Sent: Wednesday, December 19, 2001 2:24 PM
Subject: Re: [Zope-dev] disabling gc does not necessarily hide
memorycorruption


>
> On Wed, 2001-12-19 at 13:34, Chris McDonough wrote:
> > It would be good if someone who is experiencing random crashes could
confirm
> > that the the new compiler package fixes their problem.
>
> I might risk losing a few more points with my sysadmin to test it (Hi
> daniduc :-) if there was an easily downloadable package with clear
> instructions on how to apply it to Zope 2.4.3 (I don't feel like messing
> with CVS for this), and if you tell me that it won't corrupt my Data.fs
> or anything :-)
>
> Cheers, Leo
>
> --
> Ideas don't stay in some minds very long because they don't like
> solitary confinement.
>
>
> _______________________________________________
> 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 )
>