- Zope-Dev - Zope lists

Come to the Zope Sprint @ PyCon 2009
by Lennart Regebro 20 Feb '09

20 Feb '09

There will be a Zope + Friends sprint @ PyCon 2009, to work on Zope and Zope-related technologies like Grok, Repoze, Deliverence etc. http://us.pycon.org/2009/sprints/projects/zope/ Because of the Repoze overlap with WSGI based frameworks we plan to work closely together with the WSGI/Pylons/TurboGears/Repoze sprint happening at the same time, so this will be a supercool webframwork sprint! Everyone is welcome! It is not necessary to sign up beforehand, but it is recommended for planning purposes. Either put your name on the wiki-page yourself, or mail me and I will add you. http://us.pycon.org/2009/sprints/projects/zope/ For general information on the sprints, see: http://us.pycon.org/2009/sprints/ or ask me. Help out / Learn / Have fun! -- Lennart Regebro http://regebro.wordpress.com/ +33 661 58 14 64

1 0

Single Sign On
by Shane Hathaway 19 Feb '09

19 Feb '09

I'm working with a customer on a single sign on (SSO) system for Zope. We haven't yet chosen which SSO system we want to use. I would like to hear from anyone who has set up SSO with Zope. We have some definite requirements: * We can't accept arbitrary identities like OpenID normally does. We need to set up our own identity provider (IDP) and force our servers to accept only identities provided by our own IDP. * The SSO process should be very similar to an ordinary cookie-based login process. I don't want the user to have to enter their username on one form and their password on another, but that's the standard OpenID process. * This will be implemented in Zope 3. We are considering OpenID, Shibboleth, CAS, and any other mature system that others might suggest. Shibboleth seems like the most obvious fit, but it's nowhere near as popular as OpenID. I haven't yet looked at CAS in detail. Alternatively, I have wondered if we actually need full-blown SSO; perhaps a carefully constructed domain-wide cookie would do the trick. Any experiences with that? Thanks to anyone who participates. Shane

5 10

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 19 Feb '09

19 Feb '09

Summary of messages to the zope-tests list. Period Wed Feb 18 12:00:00 2009 UTC to Thu Feb 19 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 18 20:59:47 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011144.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Wed Feb 18 20:45:39 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011137.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:47:43 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011138.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:49:44 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011139.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:51:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011140.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:53:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011141.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Wed Feb 18 20:55:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011142.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Wed Feb 18 20:57:46 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011143.html

1 0

zc.selenium Zope2 support
by Wolfgang Schnerring 19 Feb '09

19 Feb '09

Hello, On http://svn.zope.org/zc.selenium/branches/wosc-zope2/ I've worked to make zc.selenium be usable in Zope2/Five. There are two big changes, apart from having to sprinkle some try/except imports and other small compatibility bits around: 1. Since Zope2 insists quite firmly on running in its own process, the current way reporting of test results to the runner via a thread-shared queue is not possible. Instead, I've integrated a small HTTP serving part into the runner that the browser can POST the results to. This should incur no additional overhead, since the previous way was "browser POSTs to zope-side view which puts the results into the queue" and now it's "browser POSTs to runner-side view which puts the results into the queue". 2. I moved from "class-based resources" to simply use views (for "*"), since the Five/Zope2 machinery gave me lots of trouble that just disappeared once I switched to views instead of trying to trick resources into acting like views. I think for zc.selenium-users (who inherit from pytest.Test or use the <test:seleniumTest> directive) the change should be completely backward-compatible. Could someone please review the branch and check what's missing for it to be merged to the trunk? Thanks, Wolfgang -- Wolfgang Schnerring · ws(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development

1 0

Proposed Patch for zope.site
by Shane Hathaway 19 Feb '09

19 Feb '09

Today I ran into an exception masked by Zope 3. I found the code that was masking the exception and fixed it locally, but since this small bit of code has no docs or tests, I can't be sure I won't break stuff if I check in my change. What do y'all think I should do? Here is the patch: Index: src/zope/site/hooks.py =================================================================== --- src/zope/site/hooks.py (revision 96718) +++ src/zope/site/hooks.py (working copy) @@ -91,10 +91,7 @@ def adapter_hook(interface, object, name='', default=None): - try: - return siteinfo.adapter_hook(interface, object, name, default) - except zope.component.interfaces.ComponentLookupError: - return default + return siteinfo.adapter_hook(interface, object, name, default) def setHooks(): Catching ComponentLookupError is a problem when an adapter factory looks up another adapter. If the first adapter lookup succeeds but the second fails with a ComponentLookupError, the current code makes it look like the first adapter is not registered at all. Very confusing. This patch exposes the correct traceback. I think my patch is correct because the 'default' parameter implies to me that if 'siteinfo.adapter_hook' can't find an adapter, it will return None, not raise ComponentLookupError. If 'siteinfo.adapter_hook' does in fact raise ComponentLookupError, then something else must be wrong and we should report the exception. BTW, until recently, this module lived in zope.app.component. It looks like this exception masking originated in Subversion revision 26391. Shane

1 0

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 18 Feb '09

18 Feb '09

Summary of messages to the zope-tests list. Period Tue Feb 17 12:00:00 2009 UTC to Wed Feb 18 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Tue Feb 17 20:57:52 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011136.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Tue Feb 17 20:43:34 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011129.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 17 20:45:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011130.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 17 20:47:45 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011131.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 17 20:49:51 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011132.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 17 20:51:51 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011133.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Tue Feb 17 20:53:52 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011134.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 17 20:55:52 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011135.html

1 0

Re: [Zope-dev] SVN: zope2book/trunk/ Lot's of updates over the weekend!
by Tres Seaver 17 Feb '09

17 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Log message for revision 96569: > Lot's of updates over the weekend! > > > Changed: > A zope2book/trunk/TODO.txt > A zope2book/trunk/old/ > A zope2book/trunk/old/AdvDTML.rst > A zope2book/trunk/old/DTML.rst > U zope2book/trunk/source/Acquisition.rst > D zope2book/trunk/source/AdvDTML.rst I think it is too premature to be moving the DTML chapters out of the book: if we arent just updating the book to be current with 2.12, then we probably need to discuss what kind of book we want, before chopping it apart. At the moment, the book is largely a guide to what can be done with Zope TTW. DTML is still part of that store: it isn't gone, nor even deprecated: its just that most core developers prefer not to use it in most cases. Note that there is still no replacement for DTML for at least one major TTW use case (SQL methods). Rewriting the "when to use ZPT vs. DTML bits, and making them more prominent earlier in the book, would be a sensible change. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJmDiA+gerLs4ltQ4RAhIHAKCzo/z1InRyAx5rz2GI0grrHwC9/ACfa6oL 4YOVh5HtzRuLYEkhCDNncpE= =LDwp -----END PGP SIGNATURE-----

6 5

Zope Tests: 7 OK, 1 Failed
by Zope Tests Summarizer 17 Feb '09

17 Feb '09

Summary of messages to the zope-tests list. Period Mon Feb 16 12:00:00 2009 UTC to Tue Feb 17 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 16 20:57:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011128.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Feb 16 20:43:25 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011121.html Subject: OK : Zope-2.9 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 16 20:45:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011122.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 16 20:47:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011123.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 16 20:49:26 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011124.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 16 20:51:27 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011125.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Mon Feb 16 20:53:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011126.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 16 20:55:28 EST 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-February/011127.html

1 0

zope.testing tests failing on trunk (using Python 2.4.6 and 2.5.4)
by Gary Poster 16 Feb '09

16 Feb '09

zope.testing trunk has five tests failing in Python 2.4.6 and four failing in Python 2.5.4 (on self-compiled versions on Mac OS X). Anyone know what the story is here? Gary

2 2

Optional patching in z3c.ptcompat
by Malthe Borch 16 Feb '09

16 Feb '09

Just a note that the upcoming release of z3c.ptcompat will have a module which monkey-patches ``zope.app.pagetemplate``, such that the view page template classes use z3c.pt for rendering (just committed to trunk). This is an optional behavior which may ease transition to Chameleon. Note that ``five.pt`` does this by default (for Zope 2 deployments). \malthe

1 0