January 2010 - Zope-Dev

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

12 Jan '10

Summary of messages to the zope-tests list. Period Mon Jan 11 12:00:00 2010 UTC to Tue Jan 12 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 11 20:36:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013365.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Jan 11 20:38:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013366.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:40:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013367.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:42:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013368.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:44:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013369.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Jan 11 20:46:38 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013370.html

1 0

patterns for using sphinx with the Zope Toolkit?
by Martijn Faassen 12 Jan '10

12 Jan '10

Hi there, I am interested in creating sphinx-driven documentation for Zope Toolkit packages. I'd like to maintain the documentation for a package (say, zope.component) in that package, in a 'doc' directory. I'm wondering what experiences people have with maintaining Sphinx docs. I've used plain Sphinx before, but are there any buildout recipes people recommend, for instance? It'd also be interesting to explore using Manuel - how would one add manuel-based testing to a Sphinx documentation tree? I'd like to give the priority to testing documentation samples as opposed to doctest-driven testing. I also want to be careful: sometimes the doctest setup fluff tends to distract from clear documentation, and sometimes the effort in composing doctests will slow down writing documentation. I'd therefore want manuel-tested sample code to be incremental. I want to be able to start out with purely untested sample code and then gradually convert *some* samples over to Manuel. How could we support that pattern? Ideas and opinions? This will also help me write the "writing Zope Toolkit documentation" document. :) Regards, Martijn

8 20

windows newslines in doctests
by Chris Withers 11 Jan '10

11 Jan '10

Hi All, I've run into problems with Windows newlines in doctests a couple of times now and so thought I'd ask what people do in general to work around this... Do you: - make sure .txt that ends up being doctested only has \n line endings in it? - use zope.testing.renormalizing to replace \r\n with \n? - something else I'm not aware of :-) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk

3 9

Re: [Zope-dev] Stepping back as Zope 2 release manager
by Kit BLAKE 11 Jan '10

11 Jan '10

2010/1/11 Andreas Jung <lists(a)zopyx.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi there, > > I would like to inform you that I intent to retreat from the Zope 2 > release manager position soon. I have been serving the Zope community in > this position for almost seven years and now it is time to move on and > hand > over the responsibility to some other person. The reasons for stepping > down > are pretty easy: I am too busy with other things and I would like to > shift my > focus on other Zope-related projects but I will remain part of the > Zope and > Plone community. > > The Zope community has no official process for choosing a new release > manager so > I assume some volunteer has to speak up or someone may suggest a > honorable person > of the Zope community for the position. Thanks for the years of contributions and time! Many people and parties have appreciated it. Good luck with the new endeavors, Kit -- Kit BLAKE · Infrae · http://infrae.com/ + 31 10 243 7051

2 1

zope.app.form and zope.formlib
by Martijn Faassen 11 Jan '10

11 Jan '10

Hi there, I've been trying to clean up the zope.formlib/zope.app.form situation. This is a report about my lack of progress so far, just so I have something to show for it. :) zope.app.form is in practice in use as a widget library for zope.formlib. It however also contains code that supports the original Zope 3 form system (using ZCML directives). My first response was to try to move zope.app.form's widgets into zope.formlib. zope.app.form can then depend on zope.formlib for its widgets (for backwards compatibility), and zope.formlib would stop depending on zope.app.form. We can leave the old Zope 3 form system behind. I started to try this but was daunted by having to port a huge amount of code from zope.app.form to zope.formlib, including test code. Instead, I tried to create a zope.formlibwidget which which would contain only the widgets of zope.app.form. zope.app.form would then depend on it for backwards compatibility, and zope.formlib would only need to depend on zope.formlibwidget. Unfortunately this bounced off the fact that zope.app.form's functional widget tests (there are many, we want to retain them) depend on the old Zope 3 form support in order to do their tests. The old Zope 3 form support I was trying to get rid of in the first place. To do sane functional tests I need a form library. I can't use zope.formlib in zope.formlibwidget as that would create a circular dependency (at least for tests, but that's ugly enough). So my conclusion is to move zope.app.form's widget stuff into zope.formlib, so that the functional tests can be ported to use zope.formlib instead of the old Zope 3 form system. So I'm back to my original approach again... Regards, Martijn

4 4

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

11 Jan '10

Summary of messages to the zope-tests list. Period Sun Jan 10 12:00:00 2010 UTC to Mon Jan 11 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 10 20:37:05 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013359.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Jan 10 20:39:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013360.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 10 20:41:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013361.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 10 20:43:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013362.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 10 20:45:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013363.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Jan 10 20:47:06 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013364.html

1 0

Technical Decisions
by Baiju M 11 Jan '10

11 Jan '10

Hi All, Here are few technical decisions I made so far: http://svn.zope.org/bluebream/trunk/docs/source/notes.txt?view=markup Looking for your feedback and comments. - BlueBream is a "web framework". - BlueBream can be called as Bream or BB for short. - The only public API exposed by "bluebream - the package" is an entry point:: "paste.paster_create_template": ["bluebream = bluebream.template:BlueBream"] The implementation of "bluebream" template is defined in "bluebream.template.BlueBream". The template implementation location could be changed if required later. This leaves us an option to change "bluebream" as a namespace package if required. - All the framework code will be using "zope" or "zope.app" namespace packages. Although "bream" could be considerd as a namespace package in future. - "bluebream" the project consists - documentation - compatibility test suite - project template May be documentation and compatibility test suite could be separated out to separate locations/packages later. - BlueBream 1.0 should provide an upgradation path from Zope 3.4 ZTK - Any "shell command" which developer need to repeat later should not be automated by the project template. - Running ``bootstrap.py`` and ``buildout`` inside project should not be added to project template creation for the previous reason. A suporting reason why it should not be added is to make adding sources to version controlling system should not be difficult. Regards, Baiju M

2 2

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

10 Jan '10

Summary of messages to the zope-tests list. Period Sat Jan 9 12:00:00 2010 UTC to Sun Jan 10 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 9 20:37:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013353.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Jan 9 20:39:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013354.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 9 20:41:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013355.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 9 20:43:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013356.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 9 20:45:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013357.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Jan 9 20:47:14 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013358.html

1 0

New Zope 3 name: BlueBream
by Baiju M 09 Jan '10

09 Jan '10

Hi All, I am proposing to call "Zope 3 - the web frame work" as "BlueBream". The main use for name is documentation. But the package named "bluebream" will not provide any part of framework code by itself. All the framework code will be in "zope" and "zope.app" namespaces. BTW, the original meaning of "BlueBream" is same as that of "Zope": http://en.wikipedia.org/wiki/Abramis_ballerus Regards, Baiju M

25 50

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

09 Jan '10

Summary of messages to the zope-tests list. Period Fri Jan 8 12:00:00 2010 UTC to Sat Jan 9 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: Fri Jan 8 20:38:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013347.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Jan 8 20:40:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013348.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 8 20:42:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013349.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 8 20:44:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013350.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 8 20:46:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013351.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Jan 8 20:48:32 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-January/013352.html

1 0