January 2006 - Zope-Dev

Removing 'inst'
by Philipp von Weitershausen 16 Jan '06

16 Jan '06

Tim Peters wrote: > Log message for revision 41291: > Pain, pain, and more pain. > > The build-the-installer process now completes, and running > the installer creates something that may or may not be a > working Zope. It starts fine as a Windows Service, and at > least "looks like a Zope" ;-) All hail Tim Peters! :) > Nothing in the build-the-Windows-installer process here > uses anything in the root of the inst/ directory anymore. > Instead the WinBuilders zope.mk builds Zope all by itself, > using the Python created by python.mk. Everything these > used to use in the root of the inst/ directory was so out > of whack with current reality that there was no point even > trying to reverse-engineer what it thought it was doing. It seems that 'inst' holds nothing of value anymore except 'Makefile.in' and 'WinBuilders'. I propose moving those two items to the root and remove 'inst'. Philipp

3 5

Seeking brave souls to try Zope 2.9 Windows installer
by Tim Peters 15 Jan '06

15 Jan '06

Most of the last two days I've been whacking on Zope 2.9 to build a "Zope 2 style" Windows installer that bundles Python 2.4.2, and cooperates with the new zpkgtools-created tarball layout. The build-the-Windows-installer code got simpler as a result, but ... This work is being done on branch: //svn.zope.org/repos/main/Zope/branches/tim-2.9-windows-installer which was branched off the 2.9 tag. All changes on the branch are under inst/WinBuilders/, so the idea is that when "this works", it can be merged into the 2.9 tag as well as the trunk (the stuff under WinBuilders/ isn't used for anything except building a Windows installer, and on the 2.9 tag the WinBuilders/ part is wholly broken). It's in a state now where it's not obviously broken to my eyes, but I have little experience running Zope2 so my eyes aren't reliable here. People on Windows who want to try it, knowing in advance that it may be broken in various ways, can download an experimental installer: Zope-Experimental-2.9.0-win32.exe from my member page: http://www.zope.org/Members/tim_one Please report problems to zope-dev, not to me directly. After tomorrow, I'll be on vacation for 2 weeks, and won't be terribly responsive :-) Note that I'm copying Sidnei in the hope that he can be persuaded to take up the slack. If there are problems, they're likely to be in the layout of the code: missing pieces, wrong directories, stuff like that. The 2.9 tarball's install.py installed everything it was told to install, and if there are problems there they're in Zope 2.9, not in the chain of code building the Windows installer. Nevertheless, the Windows installer could be taught to patch over them. And, of course, the build-the-installer dance may introduce new errors of its own. I hope it works for someone ;-)

3 5

Zope tests: 6 OK, 2 Failed
by Zope tests summarizer 15 Jan '06

15 Jan '06

Summary of messages to the zope-tests list. Period Sat Jan 14 12:01:02 2006 UTC to Sun Jan 15 12:01:02 2006 UTC. There were 8 messages: 8 from Zope Unit Tests. Test failures ------------- Subject: FAILED : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:10:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004016.html Subject: FAILED : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:12:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004017.html Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:01:39 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004010.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:03:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004011.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:04:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004012.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:06:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004013.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:07:40 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004014.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Sat Jan 14 21:09:10 EST 2006 URL: http://mail.zope.org/pipermail/zope-tests/2006-January/004015.html

1 0

Re: Putting pullparser and clientform where they belong (reverting 39890)
by Philipp von Weitershausen 15 Jan '06

15 Jan '06

Brian Sutherland wrote: > Since we are close to the release, I felt compelled to ask before I did > this. Could I revert 39890 [1] for the 3.2 release? > > It seems that phillip finished zpkg's module support some time ago [2]. > > (I ask as this is causing me headaches doing the Debian packaging for > the latest zope3) > > [1] http://mail.zope.org/pipermail/zope3-checkins/2005-November/026485.html > [2] http://mail.zope.org/pipermail/zpkg/2005-November/000077.html Sorry for replying to this so late, I only stumbled upon this recently. While I agree that the sys.modules/sys.path mangling was bad, this now raises the problem of correctly stitching in pullparser and ClientForm into Zope 2. Unfortunately, svn:externals doesn't work with files, so we'll have to make copies. They will have to be updated whenever pullparser and ClientForm have been updated and a newer Zope 3 is stitched in. Philipp

1 0

zpkgsetup
by Shane Hathaway 15 Jan '06

15 Jan '06

I just updated a trunk checkout of Zope 2. When I use 'python setup.py build_ext -i', I get this: Traceback (most recent call last): File "setup.py", line 32, in ? import zpkgsetup.package ImportError: No module named zpkgsetup.package 'make' fails the same way. My checkout has nothing called zpkgsetup. Any clues? Shane

2 2

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

14 Jan '06

> sean.upton(a)uniontrib.com wrote: > > I'm pretty sure this works. > > Ok, I get it now. I misread it the first time. > > > 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?), > > I suspect the cost is in creating ghosts for all of the > persistent objects. > > No objections here--I like this patch. Thanks Shane - glad it makes sense. I don't have contributor rights - would you or anyone else be willing to gateway this diff for me and commit such changes? Thanks, Sean

1 0

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

13 Jan '06

On 1/10/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > This decision was made for Zope 2.8 (according to zLOG/__init__.py). How do you mean? As far as I can see, all the levels are still there in zLOG py. The question now is weather two of these levels should be removed, as I understand it because you don't understand why other people use them. I find that logic difficult to understand. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/

3 2

Re: [Zope-dev] Re: zLOG module deprecated
by Fred Drake 13 Jan '06

13 Jan '06

On 1/9/06, Andreas Jung <lists(a)andreas-jung.com> wrote: > ZODB defines these levels but I can not see any code in the ZODB package > that actually uses these levels. Nobody should be using the zLOG levels with the logging package, but rather use the logging package levels. So in the end, there's no need for Zope to be defining levels at all, only conventions for how the levels are used. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "There is no wealth but life." --John Ruskin

5 9

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

13 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: 2751 Blamelist: andreasjung,efge,tim_one,ykomatsu BUILD FAILED: failed test sincerely, -The Buildbot

1 0

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

13 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: 2750 Blamelist: andreasjung,anguenot,efge,mkerrin,oestermeier,tim_one,ykomatsu BUILD FAILED: failed test sincerely, -The Buildbot

1 0