- Zope-Dev - Zope lists

Legal formalities to accept log and design
by Baiju M 27 Jan '10

27 Jan '10

Hi, I would like to know the legal formalities required to accept a logo (with special font). Also I would like to know the same for web design. Is there any guideline for Zope Foundation ? BlueBream team want to use a logo designed by an external person: http://muthukadan.net/bluebream/bluebream-logo-v1.png The font used there (Perizia: http://fedoraproject.org/wiki/Perizia_fonts) is designed by the same designer and released under GPL. One of my friend has offered a web design for the site (not done yet). Regards, Baiju M

6 13

zope.testing coverage support
by Martin Aspeli 26 Jan '10

26 Jan '10

Hi, A couple of questions about zope.testing's --coverage option: 1. When specifying the coverage output directory, I have to specify an absolute path: ./bin/test -s plone.caching --coverage="$(pwd)/coverage" works ./bin/test -s plone.caching --coverage="coverage" does not. Is this intentional? It took me ages to figure out this was necessary. 2. Is there anything that can read the coverage output files and present them with syntax highlighting and highlight problem areas? I know other tools (like Cobertura) have this. Is there a standard, or is it a custom format? 3. I get coverage reporting for my tests (i.e. it lists coverage of the tests package). The PyPI page for zope.testing talks about ignoring tests, but that part of the doctest is not useful as documentation. Is this a bug or a feature or something I'm supposed to be specifying on the command line? I'm using zope.testing-3.7.7, which is what comes with Zope 2.12. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

5 9

zope.testing 3.8.7: downgrade the deprecation warning
by Marius Gedminas 26 Jan '10

26 Jan '10

I got tired of seeing things like /home/mg/tmp/buildout-eggs/zope.testing-3.8.6-py2.5.egg/zope/testing/testrunner/debug.py:23: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest and since zope.testing's trunk hasn't got the problem fully licked yet (importing zope.testing.renormalizing causes a deprecation warning about zope.testing.doctest), I created a 3.8 branch based on the last public zope.testing release (3.8.6), downgraded the DeprecationWarning into a PendingDeprecationWarning, and released zope.testing 3.8.7. zope.testing's trunk is henceforth known as 3.9.0pre. Any ideas about fixing the deprecation warning caused by renormalizing.py? All it does is 'import doctest' which, due to Python's unfortunate import semantics, is interpreted as 'from zope.testing import doctest' Perhaps a from __future__ import absolute_import would help at the top? But it's only availably starting from Python 2.5, and I think zope.testing wants to be compatible with Python 2.4 too. Ideas? Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 26 Jan '10

26 Jan '10

Summary of messages to the zope-tests list. Period Mon Jan 25 12:00:00 2010 UTC to Tue Jan 26 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 25 20:36:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013449.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 25 20:38:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013450.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:40:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013451.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:42:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013452.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:44:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013453.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 25 20:46:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013454.html

1 0

quitting the ZTK steering group
by Martijn Faassen 26 Jan '10

26 Jan '10

Hi there, This is to announce my withdrawal from the Zope Toolkit steering group. I withdraw from the Zope Toolkit steering group for two reasons: * The steering group is not working as a group. Most steering group members haven't been doing much steering. This left me by myself to try to give direction. I cannot blame the others for committing their time differently, but this isn't the balance of work I signed up for. * Trying to steer the ZTK took a large amount of my energy. The discussions are quite draining and the benefit to me has not been worth the frustration. In the past year we've made large changes to the dependency structure of packages, cleaning it up. We've also improved compat testing and dependency analysis infrastructure a lot. That's the technical part. The community consequences are also important. We've been able to redefine the focus of various projects under the Zope umbrella. Separating the concern of the ZTK from Zope 3 made another refocusing project like BlueBream possible, and made more clear the relation Grok and Zope 2 have with the libraries in the ZTK. I think there is a lot more that can be done, but I don't want to feel responsible for it. Here is my analysis of problems with the ZTK: * Unclear leadership situation. I tried to resolve this by founding the ZTK project and steering group in the first place. Besides the time investment problems mentioned before, this (my?) leadership is also not fully accepted, or its judgment is not fully trusted. * Even though endless discussions take place, communication is frequently poor and frustrating at the same time. Bigger changes take too much energy to discuss. People give up even trying to cooperate and do it alone as it's a way to get things done. This creates a vicious cycle. * The commitment of parties to work together on the ZTK is fragile. Witness Zope 2 withdrawing from the ZTK quickly after some disagreements (with me). My commitment to leading the ZTK as a community project has now disappeared as well. I am primarily interested in the development of Grok. I came to the ZTK to tackle important issues for Grok, and now am going to focus my attention on Grok again. This means that I may contribute to the vicious cycle I mentioned above, but so be it. What this means for the ZTK or the steering group I do not know. The ZTK matters to me as a foundation to Grok. In a wider sense, I believe that a broader base of people using the ZTK is good for the Zope community and Grok as well. I also believe a person or group who offers leadership and has a final say is healthy for the project -- just random interested people voting -1 or +1 or -1000 or +1000 on the mailing list is a recipe for stagnation. We will have to see what the steering group, or anyone else, will come up with. I've tried to ignore zope-dev as much as possible recently, because I don't want to be dragged back into sometimes frustrating discussions. If you want to reach me you can email me or talk on grok-dev. Good luck, everybody. Martijn

6 5

Zope 3.4 and the way forward
by Marius Gedminas 26 Jan '10

26 Jan '10

So, what's the way forward for existing Zope 3.4 (KGS) users? Rewrite our apps so we don't depend on anything in zope.app and switch to the ZTK? Band together and release a Zope 3.5 KGS, which would be a strict superset of the ZTK 1.0? Band together and release a ZopeApp 1.0 KGS which would be a strict superset of the ZTK 1.0? (In which case, why not call it Zope 3.5 KGS?) Forget all this open-source sharing stuff and maintain our own separate versions.cfg files with ad-hoc version mixes? Personally, I'd prefer option 1 (if there were docs to tell me what to do to get rid of zope.app, which is implausible) or option 2. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development

5 4

Adapter registration in ZCML provides IUserPreferredCharsets lost ?
by Baiju M 26 Jan '10

26 Jan '10

Hi All, There was an adapter registration provides IUserPreferredCharsets. I can see it has moved to zope.i18n.locales with some others here: http://svn.zope.org/zope.app.i18n/trunk/src/zope/app/i18n/configure.zcml?re… But, I cannot see it ever reached here ? http://svn.zope.org/zope.i18n/trunk/src/zope/i18n/locales/configure.zcml?re… Can I add it there ? Instead of "zope.app.publisher.browser.ModifiableBrowserLanguages", I will use the new location: "zope.publisher.browser.ModifiableBrowserLanguages" Regards, Baiju M

4 4

Zope Tests: 6 OK
by Zope Tests Summarizer 25 Jan '10

25 Jan '10

Summary of messages to the zope-tests list. Period Sun Jan 24 12:00:00 2010 UTC to Mon Jan 25 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jan 24 20:37:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013443.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jan 24 20:39:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013444.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 24 20:41:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013445.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 24 20:43:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013446.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 24 20:45:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013447.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 24 20:47:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013448.html

1 0

buildout + debugzope + wsgi
by Adam GROSZER 24 Jan '10

24 Jan '10

Hello, What do we use nowadays instead of the good old debugzope script with buildout and wsgi (and paster)? I somehow did not find a recipe for that. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Finagle's third Law: In any collection of data, the figure most obviously correct, beyond all need of checking, is the mistake.

3 4

Zope Tests: 6 OK
by Zope Tests Summarizer 24 Jan '10

24 Jan '10

Summary of messages to the zope-tests list. Period Sat Jan 23 12:00:00 2010 UTC to Sun Jan 24 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jan 23 20:36:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013437.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jan 23 20:38:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013438.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:40:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013439.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:42:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013440.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:44:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013441.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 23 20:46:58 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013442.html

1 0