November 2008 - Zope-Dev

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 04 Nov '08

04 Nov '08

Summary of messages to the zope-tests list. Period Mon Nov 3 12:00:00 2008 UTC to Tue Nov 4 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=2) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 3 21:10:28 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010422.html Subject: FAILED (failures=2) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Mon Nov 3 21:11:58 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010423.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Mon Nov 3 21:04:25 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010418.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 3 21:05:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010419.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 3 21:07:27 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010420.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Mon Nov 3 21:08:57 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010421.html

1 0

ZCatalog caching with memcached
by Hedley Roos 03 Nov '08

03 Nov '08

Hi all The past few weeks I've been optimizing a busy Plone site and so collective.catalogcache was born. It uses memcached as a distributed ZCatalog cache. It is currently in production and seems to be holding just fine. The site went from being unusable to serving quite a bit of data. I'll modify it in future to not be too tied to just memcached, but that's still some way off. BTW, if you do not have memcached available the catalog functions as usual. It's only been tested for Zope 2.9.6 - 2.10.6. The repo is at http://dev.plone.org/collective/browser/collective.catalogcache. The URL may contain the word Plone but it's all Zope :) The readme contains more info and instructions. The product is a monkey patch to Catalog.py. I'd love some feedback and suggestions. Hedley

13 41

zc.relationship 1.0.2 typo bug
by Rudá Porto Filgueiras 03 Nov '08

03 Nov '08

I found a typo bug in zc.relationship 1.0.2 (pypi and svn tag 1.02). It's fixed in trunk but not backported and plone.app.relations-1.0b2 unittest found this bug. patch: Index: src/zc/relationship/shared.py =================================================================== --- src/zc/relationship/shared.py (revisão 92754) +++ src/zc/relationship/shared.py (cópia de trabalho) @@ -190,7 +190,7 @@ return None if not isinstance(depth, (int, long)) or depth < 1: raise ValueError('invalid minDepth', depth) - return lambda relchain, query, index, cache: len(relchain) >= minDepth + return lambda relchain, query, index, cache: len(relchain) >= depth class AbstractContainer(persistent.Persistent): def __init__(self, unittest exception: ---------------------------------------------------------------------- File "/home/ruda/baquara-virtual/eggs/plone.app.relations-1.0b2-py2.4.egg/plone/app/relations/README.txt", line 186, in README.txt Failed example: sorted([repr(r) for r in chains]) Exception raised: Traceback (most recent call last): File "/home/ruda/baquara-virtual/parts/zope2/lib/python/zope/testing/doctest.py", line 1348, in __run compileflags, 1) in test.globs File "<doctest README.txt[51]>", line 1, in ? sorted([repr(r) for r in chains]) File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/shared.py", line 317, in _resolveRelationshipChains for i in iterable: File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/shared.py", line 284, in _forward for i in iterable: File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/index.py", line 619, in _yieldRelationshipTokenChains if (checkTargetFilter is None or File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/index.py", line 468, in checkTargetFilter return targetFilter(relchain, query, self, targetCache) File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/shared.py", line 193, in <lambda> return lambda relchain, query, index, cache: len(relchain) >= minDepth NameError: global name 'minDepth' is not defined ---------------------------------------------------------------------- File "/home/ruda/baquara-virtual/eggs/plone.app.relations-1.0b2-py2.4.egg/plone/app/relations/README.txt", line 353, in README.txt Failed example: list(target.getSources(relation=u'relation 1', maxDepth=2, minDepth=2)) Exception raised: Traceback (most recent call last): File "/home/ruda/baquara-virtual/parts/zope2/lib/python/zope/testing/doctest.py", line 1348, in __run compileflags, 1) in test.globs File "<doctest README.txt[97]>", line 1, in ? list(target.getSources(relation=u'relation 1', maxDepth=2, minDepth=2)) File "/home/ruda/baquara-virtual/eggs/plone.relations-1.0b5-py2.4.egg/plone/relations/lazylist.py", line 315, in __len__ return len(self._data) File "/home/ruda/baquara-virtual/eggs/plone.relations-1.0b5-py2.4.egg/plone/relations/lazylist.py", line 189, in __len__ return len(self._extract_to(-1)) File "/home/ruda/baquara-virtual/eggs/plone.relations-1.0b5-py2.4.egg/plone/relations/lazylist.py", line 170, in _extract_to thelist = [i for i in self] # invokes __iter__ which sets _list File "/home/ruda/baquara-virtual/eggs/plone.relations-1.0b5-py2.4.egg/plone/relations/lazylist.py", line 158, in __iter__ for item in self._iter: File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/index.py", line 525, in _yieldValueTokens getQueries, findCycles=False): File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/index.py", line 619, in _yieldRelationshipTokenChains if (checkTargetFilter is None or File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/index.py", line 468, in checkTargetFilter return targetFilter(relchain, query, self, targetCache) File "/home/ruda/baquara-virtual/eggs/zc.relationship-1.0.2-py2.4.egg/zc/relationship/shared.py", line 193, in <lambda> return lambda relchain, query, index, cache: len(relchain) >= minDepth NameError: global name 'minDepth' is not defined -- ===================================== Rudá Porto Filgueiras Weimar Consultoria http://python-blog.blogspot.com Hospedagem Plone, Django, Zope 3, Grok... http://www.pytown.com =====================================

3 3

zope.sendmail fails on windows
by Adam GROSZER 03 Nov '08

03 Nov '08

Hello Benji, Seems like your r80928 breaks windows compatibility, because it does not support os.link and os.unlink. -- Best regards, Adam GROSZER mailto:agroszer@gmail.com -- Quote of the day: Campus sidewalks never exist as the straightest line between two points.

3 2

zope.sqlalchemy: Decoupling Zope3 and SQLAlchemy commit - how? Should I?
by Hermann Himmelbauer 03 Nov '08

03 Nov '08

Hi, In one of my Zope3 projects, I use lovely.remotetask to run specific tasks in background. These tasks do lengthy database operations via zope.sqlalchemy. Currently, lovely.remotetask seems to do a Zope3 commit() at the end of the task, which also does the SQLAlchemy commit. However, some tasks consist of a loop over self-contained operations, therefore it would be handy to commit after each such operation. This way, if one of the operations fail (e.g. due to some database error, such as locking, refrential integrity violation etc.), not the whole task is rolled back but only one operation. Moreover, the probability of database locks is reduced. But, how would I do that? First of all, I'd have to catch all database error, so that lovely.remotetask does not do a rollback on its own (which errors would that be?). Then I'd have to somehow commit - should I simply do a Zope3 commit? Or should I somehow do a database commit via zope.sqlalchemy? 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: 4 OK, 2 Failed
by Zope Tests Summarizer 03 Nov '08

03 Nov '08

Summary of messages to the zope-tests list. Period Sun Nov 2 12:00:00 2008 UTC to Mon Nov 3 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 2 21:13:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010416.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sun Nov 2 21:15:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010417.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sun Nov 2 21:07:30 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010412.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 2 21:09:00 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010413.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 2 21:10:34 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010414.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sun Nov 2 21:12:04 EST 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010415.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 02 Nov '08

02 Nov '08

Summary of messages to the zope-tests list. Period Sat Nov 1 12:00:00 2008 UTC to Sun Nov 2 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 1 22:07:21 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010410.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Sat Nov 1 22:08:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010411.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Sat Nov 1 22:01:21 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010406.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 1 22:02:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010407.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 1 22:04:21 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010408.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Sat Nov 1 22:05:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-November/010409.html

1 0

Zope Tests: 4 OK, 2 Failed
by Zope Tests Summarizer 01 Nov '08

01 Nov '08

Summary of messages to the zope-tests list. Period Fri Oct 31 12:00:00 2008 UTC to Sat Nov 1 12:00:00 2008 UTC. There were 6 messages: 6 from Zope Tests. Test failures ------------- Subject: FAILED (failures=3) : Zope-trunk Python-2.4.5 : Linux From: Zope Tests Date: Fri Oct 31 22:06:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010404.html Subject: FAILED (failures=3) : Zope-trunk Python-2.5.2 : Linux From: Zope Tests Date: Fri Oct 31 22:08:18 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010405.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.7 : Linux From: Zope Tests Date: Fri Oct 31 22:00:47 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010400.html Subject: OK : Zope-2.9 Python-2.4.5 : Linux From: Zope Tests Date: Fri Oct 31 22:02:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010401.html Subject: OK : Zope-2.10 Python-2.4.5 : Linux From: Zope Tests Date: Fri Oct 31 22:03:47 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010402.html Subject: OK : Zope-2.11 Python-2.4.5 : Linux From: Zope Tests Date: Fri Oct 31 22:05:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-October/010403.html

1 0