- Zope-Dev - Zope lists

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

10 Dec '09

Summary of messages to the zope-tests list. Period Wed Dec 9 12:00:00 2009 UTC to Thu Dec 10 12:00:00 2009 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: Wed Dec 9 21:19:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013167.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Dec 9 21:21:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013168.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 9 21:23:41 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013169.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 9 21:25:51 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013170.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 9 21:27:51 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013171.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Wed Dec 9 21:29:56 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013172.html

1 0

Baiju's book on ZCA
by Christophe Combelles 09 Dec '09

09 Dec '09

Hi all ! I've finished translating Baiju's book into french (A Comprehensive Guide to Zope Component Architecture). The bzr branch is here: https://code.launchpad.net/~ccomb/zcadoc/book-fr I've also generated some HTML and PDF output: http://ccomb.gorfou.fr/static/zcadoc/zca-fr.pdf http://ccomb.gorfou.fr/static/zcadoc/zca-fr.html The english version needs more contributions, it has not been updated for a few months and some new chapters are not finished. It would be great that some volonteers help reviewing and completing this book. Christophe

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 09 Dec '09

09 Dec '09

Summary of messages to the zope-tests list. Period Tue Dec 8 12:00:00 2009 UTC to Wed Dec 9 12:00:00 2009 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: Tue Dec 8 20:38:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013161.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Dec 8 20:40:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013162.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 8 20:42:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013163.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 8 20:44:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013164.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 8 20:46:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013165.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Dec 8 20:48:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013166.html

1 0

ZCA proposal
by Gary Poster 08 Dec '09

08 Dec '09

I think I could get fully behind the following proposal that others have made (Shane I think was one of several?). IFoo.adapt(...) IFoo.utility(...) = Why? = - This is a significant improvement in terms of being memorable, as far as I'm concerned. It's also briefer, which is related. - It uses the terms we've already taught. - It is entirely backwards compatible. We don't have to poll the world and hope we didn't miss anyone. - We can make the call syntax for ``adapt`` take multiple arguments. - It is symmetric-ish. - It would potentially allow a place to hang debug/analysis calls, as I showed earlier, but let's not have that debate yet. I can put those somewhere else if I need to. = Why not tuple multi-adaptation in the __call__? = I'm somewhat surprised that some who have been loudest about not breaking backwards compatibility are OK with breaking this, given the two reports from the very small sample we have here of users. I think it is unnecessarily risky for minimal gain, particularly when we have another reasonable option. = But Gary, I thought you didn't like ``adapt``? = No, I don't. I think it is a hindrance to understanding, and I would prefer ``instance``, for example (or maybe ``create``?). That said, people disagree with me. Going along with ``adapt`` but getting this new syntax gets me a lot of improvements from my perspective. I think people on the Launchpad team would be happy with this. I would explain ``adapt`` as "look, it's a factory," but, oh well. Progress usually means compromise. = But Gary, I thought you didn't like ``utility``? = No, I don't. I already gave up on that one, since I didn't have an answer better than "singleton" and I acknowledge that it is not great (either, for different reasons). Gary

11 18

Get rid of doctest.py in zope.testing? (Was: Bootstrapping ZCA for Python 3.)
by Lennart Regebro 08 Dec '09

08 Dec '09

I started a new branch for porting zope.testing to Python 3, for several reasons, mostly because I got confused and decided starting over with a clean copy and beginning with the new Distribute python 3 support from start would make me less foncused (it worked). The branches aren't that different in the end, obviously: http://svn.zope.org/zope.testing/branches/regebro-python3-reloaded/ There are 19 tests that doesn't pass yet (and that's mostly doctest tests, so there are many actual failures), and most of those are based in formatting differences when it comes to doctests. For example: Exceptions in Python 3 print out the whole module path of the exception, while in Python 2 it's only the classname: Immediate doctest failure. This is fixable in your doctests by trapping the exception instead, which is what I've done. However: Many of the failing tests are tests to check that the doctest module works. In the other modules I've ported, the doctest module has been included because it wasn't included in Python 2.3, and could simply be dropped with Python 2.3 support. However, in zope.testing doctests are slightly modified and also tested. So many of the failing tests are tests that doctest behave properly, and that the output formatting is OK. Which, of course, it is not. There are other differences too. The diff module seems to add empty lines at the end sometimes, which bugger up the output, especially in the colorful formatter tests. Efforts to remove doctests failed on the INTERPRET_FOOTNOTES options, which the standard Python doctests doesn't support. A quick search turns out that ZODB, zc.catalog, zc.relation, zc.async, zc.sharing, zc.freeze and lovely.remotetask uses it, maybe more. I really think it's a bad idea to have a special version of doctest.py. I think we should get rid of it. That means either dropping this feature, or getting it merged into Python 2.7 and 3.2. The 2.7 beta is out now, so it's pretty urgent. I strongly suspect it's going to be practically impossible to support zope.testing from the same test-base otherwise. Opinions? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64

4 8

Zope Tests: 6 OK
by Zope Tests Summarizer 08 Dec '09

08 Dec '09

Summary of messages to the zope-tests list. Period Mon Dec 7 12:00:00 2009 UTC to Tue Dec 8 12:00:00 2009 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 Dec 7 20:38:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013155.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Dec 7 20:40:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013156.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 7 20:42:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013157.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 7 20:44:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013158.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 7 20:46:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013159.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Dec 7 20:48:21 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013160.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 07 Dec '09

07 Dec '09

Summary of messages to the zope-tests list. Period Sun Dec 6 12:00:00 2009 UTC to Mon Dec 7 12:00:00 2009 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 Dec 6 20:38:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013149.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Dec 6 20:40:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013150.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 6 20:42:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013151.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 6 20:44:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013152.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 6 20:46:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013153.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Dec 6 20:48:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013154.html

1 0

zope.testing.testrunner.debug.post_mortem and try/finally
by Ross Patterson 07 Dec '09

07 Dec '09

When a try/finally clause is (appropriately) used to do cleanup after an exception during a test run, it often tears down parts of the fixture that are needed in order to do useful post_mortem debugging of the exception, such as closing the request or db connections. What is the best way to do post_mortem debugging with the stack in the state it was at the time of the exception? For a while now, I've been repeatedly modifying eggs in my development environment at the relevant try/finally clauses to invoke post_mortem before the tear down is done, sub-optimal to say the least. :) I find myself doing it often its time to invest in a better way. Is there some Python voodoo I'm unaware of to get a post_mortem to reflect the stack before try/finally clauses? If not, is putting some sort of hook into the relevant try/finally clauses the best way to address this? If not, what should I be doing? If putting hooks into the try/finally clauses is the right way, then it would be nice to have a somewhat canonical way to do this. It would also be nice to have a way to pass something down the line so that post_mortem() only gets called once per exception. Thoughts, Ross

6 13

Zope Tests: 6 OK
by Zope Tests Summarizer 06 Dec '09

06 Dec '09

Summary of messages to the zope-tests list. Period Sat Dec 5 12:00:00 2009 UTC to Sun Dec 6 12:00:00 2009 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 Dec 5 20:38:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013143.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Dec 5 20:40:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013144.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Dec 5 20:42:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013145.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Dec 5 20:44:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013146.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Dec 5 20:46:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013147.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Dec 5 20:48:20 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013148.html

1 0

Zope Tests: 4 OK, 2 Unknown
by Zope Tests Summarizer 06 Dec '09

06 Dec '09

Summary of messages to the zope-tests list. Period Fri Dec 4 12:00:00 2009 UTC to Sat Dec 5 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Unknown ------- Subject: UNKNOWN : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Dec 4 20:48:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013139.html Subject: UNKNOWN : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Dec 4 20:50:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013140.html Tests passed OK --------------- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Fri Dec 4 20:44:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013137.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Dec 4 20:46:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013138.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Dec 4 20:52:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013141.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Dec 4 20:54:07 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-December/013142.html

4 3