- Zope-Dev - Zope lists

Re: SVN: Zope/branches/2.10/ Merge r80451 from trunk
by Philipp von Weitershausen 02 Oct '07

02 Oct '07

According to CHANGES.txt, you're fixing a bug. Where's the test that exercises that the bug fix code? (Yes, I'm going to get anal about this.) To anybody, the fix will look a bit dubious. At least I personally am wondering how simply changing the datatype in the ZConfig schema will work... A comment explaining *why* this fixes the problem would clear up any doubts. Such a commonent could very well have been placed in the above mentioned test that's missing. Please provide it. Wichert Akkerman wrote: > Log message for revision 80452: > Merge r80451 from trunk > > Changed: > U Zope/branches/2.10/doc/CHANGES.txt > U Zope/branches/2.10/lib/python/Zope2/Startup/zopeschema.xml > > -=- > Modified: Zope/branches/2.10/doc/CHANGES.txt > =================================================================== > --- Zope/branches/2.10/doc/CHANGES.txt 2007-10-01 19:48:13 UTC (rev 80451) > +++ Zope/branches/2.10/doc/CHANGES.txt 2007-10-01 20:05:49 UTC (rev 80452) > @@ -8,6 +8,9 @@ > > Bugs fixed > > + - Launchpad #147201: treat container-class in zope.conf as a string, > + making it possible to use types from extra products directories. > + > - Collector #2358: backported fix making 'Products' package a real > "namespace package" from the trunk. > > > Modified: Zope/branches/2.10/lib/python/Zope2/Startup/zopeschema.xml > =================================================================== > --- Zope/branches/2.10/lib/python/Zope2/Startup/zopeschema.xml 2007-10-01 19:48:13 UTC (rev 80451) > +++ Zope/branches/2.10/lib/python/Zope2/Startup/zopeschema.xml 2007-10-01 20:05:49 UTC (rev 80452) > @@ -242,7 +242,7 @@ > </description> > </key> > > - <key name="container-class" datatype=".python_dotted_path"> > + <key name="container-class" datatype="string"> > <description> > Change the contiainer class a (mounted) database uses on a > per-database basis to support a different container than a plain -- http://worldcookery.com -- Professional Zope documentation and training

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 02 Oct '07

02 Oct '07

Summary of messages to the zope-tests list. Period Mon Oct 1 12:00:00 2007 UTC to Tue Oct 2 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Oct 1 20:52:19 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008426.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Mon Oct 1 20:53:50 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008427.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Oct 1 20:55:20 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008428.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Oct 1 20:56:51 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008429.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Mon Oct 1 20:58:21 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-October/008430.html

1 0

products not found when initializing zodb
by Wichert Akkerman 01 Oct '07

01 Oct '07

(I've filed this at https://bugs.launchpad.net/zope2/+bug/147201 as well) For a Plone site I am using a separate ZODB for the catalog so I can tune it a bit. I do this using the standard method in zope.conf: <zodb_db catalog> mount-point /plone.org/portal_catalog container-class Products.CMFPlone.CatalogTool.CatalogTool <zeoclient> server 127.0.0.1:5010 storage 2 name catalogstorage var /srv/plone.org/buildout/parts/instance1/var </zeoclient> </zodb_db> This works perfect in a normal Zope2 instance. But when I use buildout CMFPlone is stored in a separate directory that is listed in a products line in zope.conf: instancehome /srv/plone.org/buildout/parts/instance1 products /srv/plone.org/buildout/products products /srv/plone.org/buildout/parts/productdistros products /srv/plone.org/buildout/parts/plone the result is that Zope no longer starts: Error: The object named by "Products.CMFPlone.CatalogTool.CatalogTool" could not be imported Traceback (most recent call last): File "/srv/plone.org/buildout/parts/zope2/lib/python/Zope2/Startup/datatypes.py", line 94, in importable_name package = __import__(n, g, g, component) ImportError: No module named CMFPlone which is a bit of a showstopper for this deployment. Does anyone know how this can be fixed or worked around? There is a fair amount of deep magic to the way Zope handles Products.* so I'ld like a few suggestions before I delve into the deep. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

3 2

Zope Tests: 5 OK
by Zope Tests Summarizer 01 Oct '07

01 Oct '07

Summary of messages to the zope-tests list. Period Sun Sep 30 12:00:00 2007 UTC to Mon Oct 1 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Sep 30 20:51:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008421.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sun Sep 30 20:52:38 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008422.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Sep 30 20:54:09 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008423.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Sep 30 20:55:39 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008424.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sun Sep 30 20:57:09 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008425.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 30 Sep '07

30 Sep '07

Summary of messages to the zope-tests list. Period Sat Sep 29 12:00:00 2007 UTC to Sun Sep 30 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Sep 29 20:51:36 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008416.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Sat Sep 29 20:53:06 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008417.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Sep 29 20:54:36 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008418.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Sep 29 20:56:07 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008419.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Sat Sep 29 20:57:37 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008420.html

1 0

Zope.org, and thus Zope itself, is in trouble
by Gregory Dudek 29 Sep '07

29 Sep '07

(This is a slightly edited repost from the zope general mailing list; my apologies to anybody who saw it there.) I have been a Zope developer & user for several years. Zope is great and it has had a major impact on my work. All this to say I am an experienced Zope user and supporter. I think Zope is in serious trouble and the Zope.org web site is badly in need of attention. I started using zope in 2001 at Xerox PARC and the helpful and persuasive resources at zope.org were a major factor. Today, zope.org is full of dead links and it very hard to use unless you are already experienced. Consequently, getting started with Zope today is harder now than is was, even though the actual software is better. A key factor is that based on the zope.org web site it is not apparent whether the community is healthy or not, and the general impression is that the project is stalled since so many links are dead and defunct. How can the decay in the key zope web site have gotten so bad? (In fact I am not so sure myself of the zope community health any longer, despite the ongoing zope postings here -- I hope I will find I'm wrong in this regard at least). This has direct and indirect effects including inhibiting the uptake of Zope. In my opinion, making zope.org look healthy and be usable is the MOST important obstacle for the Zope community. I believe this is both a symptom and a cause of disarray in the Zope user/ developer community. (My apologies if you think this comment is unfair, but that's how it looks to me these days.) Zope was always a bit hairy to get into, without saying anything about Plone development or Zope 3. I just want to point out that without a clear simple up-to-date main web site, and a clear story, things are looking really bad. I introduced some zope-based material in an introductory computer science course a few years ago with moderate success, but am starting to doubt it would be appropriate any longer. Also, let's not get distracted by Google and/or all the other places to find zope stuff. The fact is, Zope.org is the de facto primary destination especially for newbies. If it's in bad shape it directly impacts Zope uptake and usage. I won't bother to go on about why Zope it good technically. It is, it's cool, and I suspect anybody of this list knows it. I am not criticizing the people on this list or the other Zope developers: I have enormous appreciation for what has been built, I just would hate to see it dwindle in vitality and use. Greg ---- Appendix (Examples) Specific evidence (these are just examples; lots more can be found trivially): 1) search for something, say "user folder" on zope.org Pages you get are dated 2001, 2000, 2003, .... Let's try link 3 for the extensible user folder (one of the formerly more popular and useful items in the first few listed). Click the "more info link": dead page (Insufficient Privileges) 2) Click "Zope Products" on the sidebar. Most of the listed products are old. 3) "Resources" Sidebar Item. Click "Zope Links". -> Site Error

2 1

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 29 Sep '07

29 Sep '07

Summary of messages to the zope-tests list. Period Fri Sep 28 12:00:00 2007 UTC to Sat Sep 29 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Sep 28 20:55:31 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008414.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Sep 28 20:51:00 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008411.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Fri Sep 28 20:52:30 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008412.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Sep 28 20:54:01 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008413.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Fri Sep 28 20:57:01 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008415.html

1 0

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 28 Sep '07

28 Sep '07

Summary of messages to the zope-tests list. Period Thu Sep 27 12:00:00 2007 UTC to Fri Sep 28 12:00:00 2007 UTC. There were 5 messages: 5 from Zope Unit Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-2.10 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Sep 27 20:57:40 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008409.html Tests passed OK --------------- Subject: OK : Zope-2.7 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Sep 27 20:53:08 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008406.html Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Unit Tests Date: Thu Sep 27 20:54:39 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008407.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Sep 27 20:56:10 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008408.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Unit Tests Date: Thu Sep 27 20:59:10 EDT 2007 URL: http://mail.zope.org/pipermail/zope-tests/2007-September/008410.html

1 0

Moving the Zope (2) collector to launchpad.
by Jim Fulton 28 Sep '07

28 Sep '07

I'm going to start the process of moving the Zope 2 collector today. It will be impossible to submit issues using the existing collector. We'll announce the availability of the launchpad-based collector soon. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

4 5

Options replacing DateTime with datetime!?
by Andreas Jung 27 Sep '07

27 Sep '07

Hi, perhaps the sun burned too long on my brain today but I investigated some options for replacing DateTime with Python's datetime module. Zope 3 uses datetime and we all know that the DateTime implementation sucks. Especially the timezone implementation has a bunch of problems (count the bugtracker issues related to timezone errors). Constraints: We can not get rid of the DateTime class and its API for backward compatibility reasons. Idea: The DateTime class remains in place and uses an instance attribute to represent the original value of a DateTime object as instance of datetime. Calls to the old DateTime API are proxied to corresponding calls of the datetime API (or emulated) Efforts so far: I have some quick-and-dirty implementation that can construct the datetime instance directly within the DateTime constructor and when loading an object from the ZODB (using a custom __setstate__() implementation...could be used for an on-the-fly migration). This seems to work properly. For timezone related issues I am using pytz. However there is a problem with using pytz: the timezone names supported by pytz are sometimes different from the standard one. E.g. 'GMT+0400' is represented in pytz as '/Etc/GMT+0400'...however that seems to be solvable. Before digging deeper I would like to hear some opinions if this seems a reasonable approach? Unlikely that we can achieve 100% backward compatibility but possibly 99%....thoughts...comments? Tnx, Andreas

9 25