Zope 2.6.2 Beta 4 Released
ZOPE 2.6.2 Beta 4 Released Zope 2.6.2b4 represents a development step in the next Zope release formed with a large number of community contributions. You may download Zope 2.6.2b4 from Zope.org: http://www.zope.org/Products/Zope/2.6.2b4/ Users of the Zope source release should note that Python 2.1.3 is now the required platform. Python 2.1.3 includes a fix to an issue that could cause crashes in Zope. Users who upgrade from source MUST RUN a |make clean| and |make| command to build the proper binaries correctly; distutils will skip compilation of the library modules needed for Zope and will cause errors if they are not up to date. Particular features of interest in Zope 2.6.2b4: * Fixed a case where objects trying to check access rights on behalf of another user were unable to do so. * Fixed memory leak with Page Templates * Python 2.2 compatibility fixes * Back ports of BTrees fixes * Back ports of ZODB fixes relating to the packing of storage, where a packed database could contain an UNDO transaction which referred to data which had been discarded by the pack * A fix for fsrecover.py which prevented it from recovering any data * Fixes for collector issues 256, 514, 683, 814, 816, 875, 882, 892, 902, 928, 937, 939, 954, 956, 959, 964 For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: * http://www.zope.org/Products/Zope/2.6.2b4/CHANGES.txt * http://www.zope.org/Products/Zope/2.6.2b4/HISTORY.txt For more information on the available Zope releases, guidance for selecting the right distribution and installation instructions, please see: http://www.zope.org/Documentation/Misc/InstallingZope.html -- Matt Kromer Zope Corporation http://www.zope.com/
Hi Matt -- I encountered a problem with ZDiscussions due to a Lasy Map Instance not getting properly unwrapped. This in an unmodified portion of a long runnning hybrid ZClass/Python Product system. We have a workaround-- using the ZUBB follow-on product that seems cleaner and more stable-- but I continue to wonder about that ZDiscussion worked at all on 2.51 and earlier systems, but died on 2.6.2b3. Is this (was this) a bug that got fixed or what? Any comments helpful. I'll upgrade to 2.6.2b4 immediately.
Dennis Allison wrote:
Hi Matt --
I encountered a problem with ZDiscussions due to a Lasy Map Instance not getting properly unwrapped. This in an unmodified portion of a long runnning hybrid ZClass/Python Product system. We have a workaround-- using the ZUBB follow-on product that seems cleaner and more stable-- but I continue to wonder about that ZDiscussion worked at all on 2.51 and earlier systems, but died on 2.6.2b3. Is this (was this) a bug that got fixed or what? Any comments helpful.
I'll upgrade to 2.6.2b4 immediately.
I have no idea, sorry ... there were only 3 changes between b3 and b4, the major one having to do with access control. -- Matt Kromer Zope Corporation http://www.zope.com/
Thanks. Just wondering... -d On Fri, 18 Jul 2003, Matthew T. Kromer wrote:
Dennis Allison wrote:
Hi Matt --
I encountered a problem with ZDiscussions due to a Lasy Map Instance not getting properly unwrapped. This in an unmodified portion of a long runnning hybrid ZClass/Python Product system. We have a workaround-- using the ZUBB follow-on product that seems cleaner and more stable-- but I continue to wonder about that ZDiscussion worked at all on 2.51 and earlier systems, but died on 2.6.2b3. Is this (was this) a bug that got fixed or what? Any comments helpful.
I'll upgrade to 2.6.2b4 immediately.
I have no idea, sorry ... there were only 3 changes between b3 and b4, the major one having to do with access control.
-- Matt Kromer Zope Corporation http://www.zope.com/
participants (2)
-
Dennis Allison -
Matthew T. Kromer