Re: [Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?
Hi, Am Dienstag, den 25.04.2006, 23:50 -0400 schrieb Tres Seaver: Smells like a fix didn't get forward-ported somehow -- that looks like the same error I helped Tim find and fix for Zope 2. CC'ing the ZODB list just in case anyone there has a better memory. Here is the NEWS.txt entry for that fix: DemoStorage --- - (3.4a4) Appropriate implementations of the storage API's ``registerDB()`` and ``new_oid()`` methods were added, delegating to the base storage. This was needed to support wrapping a ZEO client storage as a ``DemoStorage`` base storage, as some new Zope tests want to do. I remembered there was a fix like that. Unfortunately that fix was ported to the 3.6 branch actually. I'm poking around myself a bit more. What I found right now is that BaseStorage accesses an attribute _oid on the Storage given as a Base to find the highest oid currently used. This is used for the new_oid implementation as a comment right before it tells. I'll keep looking and try to find a fix. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?
Hi again, Am Mittwoch, den 26.04.2006, 08:05 +0200 schrieb Christian Theune: I remembered there was a fix like that. Unfortunately that fix was ported to the 3.6 branch actually. I'm poking around myself a bit more. What I found right now is that BaseStorage accesses an attribute _oid on the Storage given as a Base to find the highest oid currently used. This is used for the new_oid implementation as a comment right before it tells. I'll keep looking and try to find a fix. Now. I found a way to fix it, by letting BaseStory in its __init__ method only do: self._oid = base._oid by changin this to read: if hasattr(base, '_oid'): self._oid = base._oid Obviously this code is the same in the 3.4 branch, but doesn't break over there, so I'm pretty sure I'm only fixing symptoms, not the real cause. Christian -- gocept gmbh co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] RFC: The browser:page compromise
On 4/25/06, Bernd Dorn [EMAIL PROTECTED] wrote: On 25.04.2006, at 20:27, Lennart Regebro wrote: At https://svn.z3lab.org/z3lab/hello/trunk there is now a page this url seems to be broken No, it works fine, but only for svn (If you don't want to check it out and test it, you can browse the code here: http://svn.z3lab.org/trac/z3lab/browser/hello/trunk/ ) -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Heads up: I'm about to merge the jim-adapter branch
I'm about to merge the jim-adapter branch. This branch has three major refactorings on it: - A redesign of the adapter registration machinery This work: o Provides some performance improvments. + Request per second improved from 7-58% for the cases I tested. + About an 45% reduction in startup time. + About a 50% reduction in time to run the tests. I think this sets the stage for additional improvements in the future. o Set the stage for a super-lookup mechanism (like Python's super builtin), and for named subscribers. - A major simplification of local component management See zope.component.interfaces.IComponentRegistry. - A flexible system for combining component registries. - A beginning of the migration of packages out of zope.app. - A new package for doing deferred imports. This allows you to make names available at the package level without creating circular imports. See zope.deferredimport and see zope.component.__init__ for examples of it's use. This package also provides a way to deprecate names in a module. I've tested the branch against a major Zope 3 application here at Zope Corporation. In doing so, I've found and fixed lots of backward compatibility issues. I encourage you to try your applications with the trunk after the merge. If you find problems, put them in the collector and we'll fix them as soon as we can. You will probably get lots of deprecatuion warnings. Enjoy. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
