January 2006 - Zope-Dev

Zope tests: 8 OK
by Zope tests summarizer 13 Jan '06

13 Jan '06

Summary of messages to the zope-tests list. Period Thu Jan 12 12:01:01 2006 UTC to Fri Jan 13 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:01:50 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003994.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:03:20 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003995.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:04:50 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003996.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:06:20 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003997.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:07:50 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003998.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:09:22 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003999.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:10:52 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004000.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Jan 12 21:12:22 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004001.html

1 0

RE: [Zope-dev] BTreeFolder2.objectIds() - accessing _tree.keys() slow
by sean.upton＠uniontrib.com 13 Jan '06

13 Jan '06

> > Hacking objectIds() as follows (diff against trunk pasted inline) - > > gettting ids off of the meta type index for all used meta types - > > seems to make things much quicker. Two questions: > > Are you sure this actually works? _mt_index.keys() is > supposed to provide a list of all meta_types used in the > folder. To get the object ids from it, you'd need something > like this: > > ids = [] > for d in self._mt_index.values(): > ids.extend(d.keys()) > > The structure of _mt_index is documented in a comment: > > _mt_index = None # OOBTree: { meta_type -> OIBTree: { > id -> 1 } } I'm pretty sure this works. The in each OIBTree in _mt_index, the keys are ids of contained objects for all respective meta types in the folder - I use self._mt_index.keys() to list all meta_types and leverage your original code that runs when spec parameter has been passed gets run every time - loops through all meta_types does a union() of set and ids for each meta_type. This returns the equivalent of running self.objectIds(spec=self._mt_index.keys()) on the current trunk/release code, which should be identical to self._tree.keys(), but much, much faster. I'm still somewhat ignorant as to why self._tree.keys() is so slow with 100k-plus objects (waking up too many persistent objects?), but using the ids stored a few layers deep in the _mt_index seems a viable alternative with the same expected return result. With a bit more effort put in, the diff pasted below should be more complete and illustrate better: Index: BTreeFolder2.py =================================================================== --- BTreeFolder2.py (revision 41285) +++ BTreeFolder2.py (working copy) @@ -341,21 +341,22 @@ # Returns a list of subobject ids of the current object. # If 'spec' is specified, returns objects whose meta_type # matches 'spec'. - if spec is not None: - if isinstance(spec, StringType): - spec = [spec] - mti = self._mt_index - set = None - for meta_type in spec: - ids = mti.get(meta_type, None) - if ids is not None: - set = union(set, ids) - if set is None: - return () - else: - return set.keys() + + mti = self._mt_index + if spec is None: + spec = mti.keys() #all meta types + + if isinstance(spec, StringType): + spec = [spec] + set = None + for meta_type in spec: + ids = mti.get(meta_type, None) + if ids is not None: + set = union(set, ids) + if set is None: + return () else: - return self._tree.keys() + return set.keys() security.declareProtected(access_contents_information,

2 1

BTreeFolder2.objectIds() - accessing _tree.keys() slow
by sean.upton＠uniontrib.com 12 Jan '06

12 Jan '06

I have very large BTreeFolder2 (CMFMember via BaseBTreeFolder in Archetypes) - has about 260k items in _tree - objectIds() is painfully slow, as is self._tree.keys() - I've casually observed using the meta type index to get the object ids is many orders of magnitude faster. Hacking objectIds() as follows (diff against trunk pasted inline) - gettting ids off of the meta type index for all used meta types - seems to make things much quicker. Two questions: 1. Can this be considered safe in all cases (I'll code this behavior on a Subclass or in a monkey patch)? 2. If yes to #1, is there an appropriate place to lobby for this to be changed, perhaps in BTreeFolder2 product itself? Index: BTreeFolder2.py =================================================================== --- BTreeFolder2.py (revision 41285) +++ BTreeFolder2.py (working copy) @@ -341,10 +341,14 @@ # Returns a list of subobject ids of the current object. # If 'spec' is specified, returns objects whose meta_type # matches 'spec'. + + mti = self._mt_index + if spec is None: + spec = mti.keys() + if spec is not None: if isinstance(spec, StringType): spec = [spec] - mti = self._mt_index set = None for meta_type in spec: ids = mti.get(meta_type, None) Thanks, Sean +----------------------------------------------------------+ Sean Upton SignOnSanDiego.com Site Technology Supervisor The San Diego Union-Tribune 619.718.5241 sean.upton(a)signonsandiego.com 350 Camino De La Reina San Diego, CA 92108 Plone Powered! plone.org ++ python.org ++ zope.org +----------------------------------------------------------+

3 2

buildbot failure in Zope branches 2.9 2.4 Windows 2000 zc-bbwin2
by buildbot＠zope.com 12 Jan '06

12 Jan '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Windows 2000 zc-bbwin2. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2735 Blamelist: andreasjung,dobe,jinty,mkerrin,oestermeier,poster,tim_one,yuppie BUILD FAILED: failed failed slave lost sincerely, -The Buildbot

1 0

buildbot failure in Zope trunk 2.4 Windows 2000 zc-bbwin6
by buildbot＠zope.com 12 Jan '06

12 Jan '06

The Buildbot has detected a failed build of Zope trunk 2.4 Windows 2000 zc-bbwin6. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2734 Blamelist: andreasjung,dobe,jinty,mkerrin,oestermeier,poster,tim_one,yuppie BUILD FAILED: failed failed slave lost sincerely, -The Buildbot

1 0

buildbot failure in Zope branches 2.9 2.4 Linux zc-buildbot
by buildbot＠zope.com 12 Jan '06

12 Jan '06

The Buildbot has detected a failed build of Zope branches 2.9 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2735 Blamelist: andreasjung,dobe,jinty,mkerrin,oestermeier,poster,tim_one,yuppie BUILD FAILED: failed test sincerely, -The Buildbot

1 0

Zope tests: 8 OK
by Zope tests summarizer 12 Jan '06

12 Jan '06

Summary of messages to the zope-tests list. Period Wed Jan 11 12:01:02 2006 UTC to Thu Jan 12 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:02:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003986.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:04:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003987.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:05:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003988.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:07:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003989.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:08:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003990.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:10:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003991.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:11:48 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003992.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Jan 11 21:13:18 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003993.html

1 0

Zope tests: 8 OK
by Zope tests summarizer 11 Jan '06

11 Jan '06

Summary of messages to the zope-tests list. Period Tue Jan 10 12:01:01 2006 UTC to Wed Jan 11 12:01:01 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:02:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003978.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:04:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003979.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:05:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003980.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:07:16 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003981.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:08:46 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003982.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:10:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003983.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:11:47 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003984.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Jan 10 21:13:17 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/003985.html

1 0

Re: [ZODB-Dev] Re: [Zope-dev] Re: zLOG module deprecated
by Lennart Regebro 10 Jan '06

10 Jan '06

On 1/10/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > This means basically keeping zLOG since it is only a very thin logging > module wrapper. So why did we deprecate zLOG? :-) Did we? It was implemented as a wrapper in 2.8, but wasn't officially deprecated until last week. ;-) I still have no opinion on the actual issue. I know what I want, but if it has too many drawbacks, I don't want it. :-) Something common between Zope3 and Zope2 would probably be a good idea. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

3 2

buildbot failure in Zope trunk 2.4 Linux zc-buildbot
by buildbot＠zope.com 10 Jan '06

10 Jan '06

The Buildbot has detected a failed build of Zope trunk 2.4 Linux zc-buildbot. Buildbot URL: http://buildbot.zope.org/ Build Reason: changes Build Source Stamp: 2702 Blamelist: andreasjung,jim,oestermeier,philikon BUILD FAILED: failed test sincerely, -The Buildbot

1 0