hanno at hannosch
Oct 8, 2009, 8:39 AM
Post #2 of 4
(323 views)
Permalink
|
On Thu, Oct 8, 2009 at 5:15 PM, John Murphy <jackie[at]zope.com> wrote:
> We recently were bit by a segfault bug in zope.security
> (https://bugs.launchpad.net/zope3/+bug/181833) when migrating an
> application from Python 2.4 to 2.6. The newest zope.security (3.7.1,
> http://pypi.python.org/pypi/zope.security/3.7.1#id1) has a fix for the
> bug.
>
> We noticed that the KGS 3.4.0b2 uses zope.security 3.4.0 and KGS
> 3.5dev uses zope.security 3.6.0, both of which are vulnerable to this
> bug. It would be great if the fixed version was incorporated into the
> KGS soon, as segfaults during garbage collection are pretty serious --
> not to mention tough to track down :)
I think you will need to update your own application specific version
set. The Zope 3 KGS is currently unmaintained. The future of the Zope
3 project is currently unknown. The last release has been eight months
ago and there is currently no active maintenance going on.
Sorry,
Hanno
_______________________________________________
Zope-Dev maillist - Zope-Dev[at]zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
|
