January 2007 - Zope-Dev

Re: ploneout - Or how using zc.buildout for a common Zope2 project might look like
by Martijn Faassen 18 Jan '07

18 Jan '07

Hey, I only caught this message earlier today, but this is really cool! It's really nice to see some zope 2 recipes and I hope they indeed will end up on svn.zope.org soon! Your workingenv recipe sounds very interesting and I should try this soon. Does it allow easy_install to be used as well? If so, what does that mean (do paths get updated?) I'll be playing with these recipes first excuse I get. :) Regards, Martijn

4 5

small catalog cleanup
by yuppie 18 Jan '07

18 Jan '07

Hi! Just want to make sure I'm not missing something: 1. IPluggableIndex ------------------ Products.PluginIndexes.interfaces.IPluggableIndex has this method: def _apply_index(request, cid=''): """Apply the index to query parameters given in 'request'. [...] """ Some implementations have an additional 'type' argument. Neither 'cid' nor 'type' are used anywhere in Zope core. The Catalog calls '_apply_index' just with the 'request' argument. That's the only place where '_apply_index' is used. Looks like 'cid' and 'type' can be safely removed from interface and implementations. 2. parseIndexRequest -------------------- The 'get' method of Products.PluginIndexes.common.util.parseIndexRequest returns the default value if the value is not true. This changes values like 0 or False to the default value. Looks like a bug to me. But fixing this changes the behavior. If there are no objections, I'll resolve these two issues on the Zope trunk. Cheers, Yuppie

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 18 Jan '07

18 Jan '07

Summary of messages to the zope-tests list. Period Wed Jan 17 12:00:00 2007 UTC to Thu Jan 18 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:08:37 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007062.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:10:08 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007063.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:11:38 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007064.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:13:08 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007065.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:14:39 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007066.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:16:09 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007067.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Wed Jan 17 21:17:39 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007068.html

1 0

Re: ploneout - Or how using zc.buildout for a common Zope2 project might look like
by Hanno Schlichting 18 Jan '07

18 Jan '07

Martijn Faassen wrote: > Hey, > > Just some feedback in case you haven't gotten this already: I have > problem running bin/buildout as it seems to fail getting workingenv.py > from the cheeseshop: > > zc.buildout.easy_install: Getting new distribution for workingenv.py>=0.3 > Page at http://www.python.org/pypi/workingenv.py/ links to .py file(s) > without version info; an index scan is required. > error: Couldn't find a setup script in /tmp/tmpDRKwglget_dist/workingenv.py > Traceback (most recent call last): Ah I had that problem with buildout as well. I could install it using my global easy_install though. Probably we need to append some '#egg=project-version' here according to http://peak.telecommunity.com/DevCenter/setuptools#dependencies-that-aren-t… as workingenv is distributed as a single Python script rather than a package. Hanno

1 0

Re: ploneout - Or how using zc.buildout for a common Zope2 project might look like
by Hanno Schlichting 18 Jan '07

18 Jan '07

Hi, sorry, I'm catching up with my mail slowly these days... Martijn Faassen wrote: > Hey, > > Martin Aspeli wrote: >> Martijn Faassen wrote: > >>> If you used a pure buildout solution you'd have gotten an ImportError on >>> elementtree that you'd need to fix by altering a setup.py somewhere. >> I did get an ImportError. The way I fixed it was by running >> 'easy_install elementtree'; perhaps I should've updated the buildout or >> the deps of one of the eggs instead. > > Right, you'd want to write this dependency down, probably in an egg > dependency if you can do it, so it gets pulled in automatically. Yep, we should note both elementree (required by Archetypes, more precisely Marshall anyways since Plone 2.5) and PIL (python-imaging) as dependencies somewhere in ploneout. > [snip] >>> So if you have a project with a setup.py called 'foo' under the buildout >>> root, you'd say this in buildout.cfg: >>> >>> [buildout] >>> develop = foo >> Aha, didn't know that. Interesting. >> >> How does that work if I then decide to add another package to the >> buildout though? Do I then end up wiping everything and starting from >> scratch (e.g. blank zope instance part) just to get that one egg to be >> installed? Scary... > > If you change the configuration of your Zope instance to include that > egg then yes, your instance will be rebuilt. Note that the object > database is in another part, so it won't be wiped. Yeah, scary. It would > be less scary if Zope instances were less complicated and if > configuration were maintained somewhere else. One thing to correct here, is that I haven't found the time to make the Data.fs and independent part, so while in the Zope3 recipes, the instance and the database are separated, they are currently not in the Zope2 recipes. There's an XXX comment in the Zope2 instance recipe, that marks the commented out section of the recipe, that would need to be adjusted. > [snip] >> I guess I don't understand how I'm supposed to use this *during >> development* where I may be finding, creating, adding and removing my >> own eggs or other old-style Products throughout the life of the problem. > > You change your dependencies in the respective setup.py files. > Considering old style Products I have no idea what the solution strategy > is of the recipes involved. Be careful here, as I noted I did not understand the way buildout's egg and develop section should really work, so my current Zope2 recipes don't use that at all. So if you are confused at some points, that's because you are not talking about the same approach ;) >> - Having to re-create the Data.fs each time is unacceptable > > It shouldn't do that unless you change the configuration of the data > section specifically. At least that's the case for the Zope 3 recipes. See above, the independent database part is still missing. >> - Having to wait half an hour while buildout re-downloads and >> re-configures everything is hardly great > > That's not what it should be doing - the Zope 2 software home shouldn't > be touched, for instance. Creating a new instance doesn't cost a lot of > time, though. Indeed, as noted somewhere I even introduces a local offline option for the Zope2 checkout recipe, so it shouldn't get downloaded or updated at all, once checked out, unless buildout thinks some configuration of that part has changed and it wipes the part completely. I'm not sure but it might be that the current recipes being in development mode themselves cause trouble here. I'm not sure how exactly buildout determines the checksum of a recipe, but if the SVN revision number is somehow involved, updating the ploneout checkout itself could cause some trouble, as the recipes are included in them as well. But this is only a wild guess ;) > You can stop it from doing redownloads (if you know it isn't necessary) > by doing: > > bin/buildout buildout:offline=true Yep, you need to know the above command. In general it will not attempt to update any part, but if buildout determines that a parts options or the underlying recipe has changed it will still wipe and rebuild from scratch. As a general comment, the current ploneout config should probably be changed to at least not include any eggs as parts, but should use buildouts approach of putting their checkout in src/ instead not managing them as a part and including all those in the develop section of buildout. Hanno (still catching up with this thread...)

1 0

synonym for getMultiAdapter
by Chris Withers 18 Jan '07

18 Jan '07

Hi All, I'd love to see: IWhatever(multi=(obj1,obj2,obj3)) ...as a sysnonym for getMultiAdapter((obj1,obj2,obj3),IWhatever) What do people feel about this? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

[testrunner] Problems with optparse?
by Andreas Jung 17 Jan '07

17 Jan '07

suxmac2:~/sandboxes/Zope/Zope ajung$ bin/zopectl test -t Products.Five Hi, I encounter some strange problems with the testrunner (testing the Zope 2 trunk): Running tests via: /opt/python-2.4.4/bin/python /Users/ajung_data/sandboxes/Zope/Zope/bin/test.py -v --config-file /Users/ajung_data/sandboxes/Zope/Zope/etc/zope.conf -t Products.Five Parsing /Users/ajung_data/sandboxes/Zope/Zope/etc/zope.conf Running tests at level 1 Test-module import failures: Module: zope.testbrowser.tests Traceback (most recent call last): File "/Users/ajung_data/sandboxes/Zope/Zope/lib/python/zope/testbrowser/__init__.py", line 20, in ? from testing import Browser File "/Users/ajung_data/sandboxes/Zope/Zope/lib/python/zope/testbrowser/testing.py", line 27, in ? from zope.testbrowser import browser File "/Users/ajung_data/sandboxes/Zope/Zope/lib/python/zope/testbrowser/browser.py", line 19, in ? from test import pystone File "/Users/ajung_data/sandboxes/Zope/Zope/test.py", line 103, in ? help="""\ File "/opt/python-2.4.4/lib/python2.4/optparse.py", line 938, in add_option self._check_conflict(option) File "/opt/python-2.4.4/lib/python2.4/optparse.py", line 913, in _check_conflict option) OptionConflictError: option --config-file: conflicting option string(s): --config-file Another error: running 'zopectl test -D' tries to debug optparse itself Running tests via: /opt/python-2.4.4/bin/python /Users/ajung_data/sandboxes/Zope/Zope/bin/test.py -v --config-file /Users/ajung_data/sandboxes/Zope/Zope/etc/zope.conf -D Parsing /Users/ajung_data/sandboxes/Zope/Zope/etc/zope.conf Running tests at level 1 optparse.OptionConflictError: option --config-file: conflicting option string(s): --config-file > /opt/python-2.4.4/lib/python2.4/optparse.py(913)_check_conflict() -> option) (Pdb) Any ideas? Andreas

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 17 Jan '07

17 Jan '07

Summary of messages to the zope-tests list. Period Tue Jan 16 12:00:00 2007 UTC to Wed Jan 17 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:08:13 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007055.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:09:43 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007056.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:11:14 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007057.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:12:44 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007058.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:14:14 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007059.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:15:44 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007060.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Tue Jan 16 21:17:14 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007061.html

1 0

Zope Tests: 7 OK
by Zope Tests Summarizer 16 Jan '07

16 Jan '07

Summary of messages to the zope-tests list. Period Mon Jan 15 12:00:00 2007 UTC to Tue Jan 16 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:11:21 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007048.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:12:52 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007049.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:14:22 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007050.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:15:52 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007051.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:17:22 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007052.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:18:52 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007053.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Jan 15 21:20:23 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007054.html

1 0

Zope Tests: 6 OK, 1 Failed
by Zope Tests Summarizer 15 Jan '07

15 Jan '07

Summary of messages to the zope-tests list. Period Sun Jan 14 12:00:00 2007 UTC to Mon Jan 15 12:00:00 2007 UTC. There were 7 messages: 7 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:16:41 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007047.html Tests passed OK --------------- Subject: OK : Zope-2.6 Python-2.1.3 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:07:40 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007041.html Subject: OK : Zope-2.6 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:09:10 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007042.html Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:10:40 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007043.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:12:10 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007044.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:13:40 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007045.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Jan 14 21:15:11 EST 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-January/007046.html

1 0