February 2010 - Zope-Dev

z3c.form and redirects
by Martin Aspeli 23 Feb '10

23 Feb '10

Hi, A lot of the forms I write perform a redirect at the end of the action handler for a successfully submitted form. z3c.form's __call__() indiscriminately calls update() and then render(). This means that even if something in update() (the action handler in this case) causes a redirect, the render() method is called, which is unnecessary since the browser will ignore the response body and perform the redirect. It also triggered a small bug in Plone (since worked around) whereby status messages would be output on the "hidden" page and go missing for the final page (status messages in Plone can be persisted across redirects using a cookie). Grok's forms do something like this: def __call__(self): self.update() if self.request.response.getStatus() not in (301, 302): return self.render() return u'' Would it be an idea for z3c.form to do the same? Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 23 Feb '10

23 Feb '10

Summary of messages to the zope-tests list. Period Mon Feb 22 12:00:00 2010 UTC to Tue Feb 23 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 Feb 22 20:36:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013617.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Mon Feb 22 20:38:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013618.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Mon Feb 22 20:40:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013619.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Feb 22 20:42:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013620.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Mon Feb 22 20:44:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013621.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Mon Feb 22 20:46:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013622.html

1 0

Re: [Zope-dev] SVN: ExtensionClass/trunk/ Merged hannosch-lp-143657 branch
by Tres Seaver 23 Feb '10

23 Feb '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hanno Schlichting wrote: > Log message for revision 109298: > Merged hannosch-lp-143657 branch > > > Changed: > U ExtensionClass/trunk/CHANGES.txt > U ExtensionClass/trunk/setup.py > U ExtensionClass/trunk/src/ExtensionClass/pickle/pickle.c > U ExtensionClass/trunk/src/ExtensionClass/tests.py > > -=- > Modified: ExtensionClass/trunk/CHANGES.txt > =================================================================== > --- ExtensionClass/trunk/CHANGES.txt 2010-02-22 17:24:07 UTC (rev 109297) > +++ ExtensionClass/trunk/CHANGES.txt 2010-02-22 17:30:41 UTC (rev 109298) > @@ -1,9 +1,11 @@ > Changelog > ========= > > -2.12.1 (unreleased) > +2.13.0 (unreleased) > ------------------- > > +- Avoid defining ``__getnewargs__`` as not to defeat the ZODB persistent > + reference optimization. Refs https://bugs.launchpad.net/zope2/+bug/143657. Is this really worth treating as a new major version? There is no API change involved, right? Just faster? 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuDILkACgkQ+gerLs4ltQ78/QCgplkyytmsXcds+h+oqdL6UNGz 6+gAoKwZqF5B5IhHl5LWD7AW6p2pzGeW =zV3S -----END PGP SIGNATURE-----

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 22 Feb '10

22 Feb '10

Summary of messages to the zope-tests list. Period Sun Feb 21 12:00:00 2010 UTC to Mon Feb 22 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 Feb 21 20:36:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013611.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sun Feb 21 20:38:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013612.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sun Feb 21 20:40:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013613.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Feb 21 20:42:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013614.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sun Feb 21 20:44:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013615.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sun Feb 21 20:46:50 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013616.html

1 0

traversal and __before_publishing_traverse__ conflict
by Wichert Akkerman 21 Feb '10

21 Feb '10

Apologies for the cross post, but since there are many components involved here I'm not sure what the right list is. Plone uses plone.theme to set an IBrowserSkinType on the request that matches the currently selected CMF skin. This is very useful since it allows you to register browser views and other components for a CMF skin. plone.theme does this by using the __before_publishing_traverse__ hook on the site root. For one site I want to offer a different skin to people coming in via a separate URL. I do this by proxying to the site and adding a ++skin++ traverser to set the skin layer. However this does not work due to how Zope 2 publication works. What happens is this: 1. ZPublisher traverses over the site root and calls the CMF __before_publishing_traverse__ hooks. Via a IBeforeTraverseEvent event plone.theme gets called and adds a IBrowserSkinType layer for the current CMF skin. 2. ZPublisher handles ++skin++name, which sets an IBrowserSkinType layer for my new skin, replacing the layer set by plone.theme. The traverser returns the same object, our site root, again. 3. ZPublishes procees by calling the __before_publishing_traverse__ for the site root again, which ends up calling plone.theme again and replacing my skin layer again. The problem here is that a ++skin++ traverser always returns the same object again, and ZPublisher will happily treat it as a new object and call all hooks for it again. The only way to avoid this that I can see is to make ZPublisher check if a traversal step returns the same object again, and if so skip the __before_publishing_traverse__ hook in that case. This feels like a safe change, but I am not sure if this would break anything. Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

1 1

Zope Tests: 6 OK
by Zope Tests Summarizer 21 Feb '10

21 Feb '10

Summary of messages to the zope-tests list. Period Sat Feb 20 12:00:00 2010 UTC to Sun Feb 21 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 Feb 20 20:37:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013605.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Feb 20 20:39:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013606.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 20 20:41:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013607.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 20 20:43:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013608.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 20 20:45:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013609.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Sat Feb 20 20:47:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013610.html

1 0

Buildout reporting 'Temporary failure in name resolution' - any clue why?
by Hermann Himmelbauer 20 Feb '10

20 Feb '10

Hi, Since some time when doing a "bin/buildout" I experience the following errors: Download error: (-3, 'Temporary failure in name resolution') -- Some packages may not be found! The problem is probably obvious - some URL may be wrong or the like, but I can't find out which one. The output looks like this (snippet): Installing 'bsp', 'zbsp', 'sdecstr', 'sa_tools', 'pybktools', 'ibanlib', 'sqlalchemy==0.5.6', 'pysqlite'. We have a develop egg: BSP 0.0.1 We have a develop egg: zbsp 0.1dev We have a develop egg: sdecstr 0.0.1 We have a develop egg: sa-tools 0.0.1 We have a develop egg: pybktools 0.0.1 We have a develop egg: ibanlib 0.0.1 We have the distribution that satisfies 'sqlalchemy==0.5.6'. Download error: (-3, 'Temporary failure in name resolution') -- Some packages may not be found! --- and 21 times the same error again --- Getting distribution for 'pysqlite'. File "build/bdist.linux-i686/egg/pysqlite2/test/py25tests.py", line 48 with self.con: ^ SyntaxError: invalid syntax zip_safe flag not set; analyzing archive contents... Got pysqlite 2.5.6. Download error: unknown url type: svn -- Some packages may not be found! Download error: unknown url type: svn -- Some packages may not be found! Getting distribution for 'lovely.remotetask'. Got lovely.remotetask 0.5. The problem seems to be somewhere in between SQLAlchemy and pysqlite (both install, however). It seems it works anyway. But these errors consume quite some time (around 10 minutes), any idea what to do? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

3 2

Zope Tests: 6 OK
by Zope Tests Summarizer 20 Feb '10

20 Feb '10

Summary of messages to the zope-tests list. Period Fri Feb 19 12:00:00 2010 UTC to Sat Feb 20 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 Feb 19 20:39:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013599.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Fri Feb 19 20:41:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013600.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Fri Feb 19 20:43:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013601.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Feb 19 20:45:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013602.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Fri Feb 19 20:47:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013603.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Fri Feb 19 20:49:57 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013604.html

1 0

Zope Tests: 6 OK
by Zope Tests Summarizer 19 Feb '10

19 Feb '10

Summary of messages to the zope-tests list. Period Thu Feb 18 12:00:00 2010 UTC to Fri Feb 19 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: Thu Feb 18 20:36:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013593.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Thu Feb 18 20:38:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013594.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Thu Feb 18 20:40:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013595.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Feb 18 20:42:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013596.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Thu Feb 18 20:44:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013597.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Thu Feb 18 20:46:41 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013598.html

1 0

release for z3c.password with Dutch translations
by Jan-Wijbrand Kolman 18 Feb '10

18 Feb '10

Hello, I would be greatly helped with a new release of z3c.password with the Dutch translations that I recently added. Would it be possible for one of the package owners to make a release, or, alternatively, allow me to upload a new version to the package index? (My pypi username is jw). Thank you very much! regards, jw

2 2