[Zope-dev] Zope Tests: 4 OK, 1 Unknown
Summary of messages to the zope-tests list. Period Wed Aug 13 11:00:00 2008 UTC to Thu Aug 14 11:00:00 2008 UTC. There were 5 messages: 1 from Mister Nice Guy, 4 from Zope Tests. Unknown --- Subject: Storesonline, Plan for an ecommerce Website. From: Mister Nice Guy Date: Wed Aug 13 09:14:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010005.html Tests passed OK --- Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 13 20:53:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010006.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 13 20:55:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010007.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 13 20:56:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010008.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Aug 13 20:58:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010009.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
Previously Zope Tests Summarizer wrote: Unknown --- Subject: Storesonline, Plan for an ecommerce Website. From: Mister Nice Guy Date: Wed Aug 13 09:14:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/010005.html That's an interesting test result :) Wichert. -- Wichert Akkerman [EMAIL PROTECTED]It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 4 OK, 1 Unknown
On Aug 14, 2008, at 13:59 , Wichert Akkerman wrote: Previously Zope Tests Summarizer wrote: Unknown --- Subject: Storesonline, Plan for an ecommerce Website. From: Mister Nice Guy Date: Wed Aug 13 09:14:30 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-August/ 010005.html That's an interesting test result :) It's a spammer who signed on to several lists yesterday, using the web confirmation so it was probably a live person, and sent spam. I noticed it when such a spam came through one of the lists I am on and unsubscribed that person from all lists. jens ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] DBTab/Mountpoint bug
Hi, Zope 2's multi-database support has a bug: it doesn't connect the registered databases into a multi-database structure unless someone traverses over the mount point objects. This makes local component registration that spans multiple database problematic because you have to first traverse over all mountpoints, before using `getUtility` etc. Here's a patch that fixes the problem. It needs to be applied to lib/python/Products/ZODBMountPoint: Index: __init__.py === --- __init__.py (revision 2957) +++ __init__.py (working copy) @@ -25,6 +25,9 @@ MountedObject.manage_getMountStatus, MountedObject.manage_addMounts,), ) - - - +# Open all DBTab databases once, so they get registered with the +# multi-database data structure and can later be opened automagically with +# ZODB's get_connection function. +dbtab = MountedObject.getConfiguration() +for name in dbtab.listDatabaseNames(): +dbtab.getDatabase(name=name) However, I don't see a good way to write a test for this. Any ideas? How do I test product initialisation code? I'd like to get this fix into in Zope 2.11. Christian -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DBTab/Mountpoint bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Theune wrote: Hi, Zope 2's multi-database support has a bug: it doesn't connect the registered databases into a multi-database structure unless someone traverses over the mount point objects. This makes local component registration that spans multiple database problematic because you have to first traverse over all mountpoints, before using `getUtility` etc. Here's a patch that fixes the problem. It needs to be applied to lib/python/Products/ZODBMountPoint: Index: __init__.py === --- __init__.py (revision 2957) +++ __init__.py (working copy) @@ -25,6 +25,9 @@ MountedObject.manage_getMountStatus, MountedObject.manage_addMounts,), ) - - - +# Open all DBTab databases once, so they get registered with the +# multi-database data structure and can later be opened automagically with +# ZODB's get_connection function. +dbtab = MountedObject.getConfiguration() +for name in dbtab.listDatabaseNames(): +dbtab.getDatabase(name=name) However, I don't see a good way to write a test for this. Any ideas? How do I test product initialisation code? Put the new code in a separate function, test that function, and then call it from within 'initialize' (i.e., don't worry about testing that it gets called). I'd like to get this fix into in Zope 2.11. +1. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIpEJk+gerLs4ltQ4RApURAKCC8WY/d0hT+PygAie+e7t3PzsppACgrmau u/+Tx9AGnerhxf5PXX5vP0c= =uyvv -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] DBTab/Mountpoint bug
On Thu, 2008-08-14 at 10:34 -0400, Tres Seaver wrote: Put the new code in a separate function, test that function, and then call it from within 'initialize' (i.e., don't worry about testing that it gets called). I thought there would be more to it and didn't think that this would solve my problem. But actually it does. Thanks for the pointer. I'd like to get this fix into in Zope 2.11. +1. :) -- Christian Theune · [EMAIL PROTECTED] gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Zope/branches/Zope-2_8-branch/lib/python/Products/PythonScripts/patches.py - integrated Hotfix-2008-08-12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
Log message for revision 89809:
- integrated Hotfix-2008-08-12
Changed:
A
Zope/branches/Zope-2_8-branch/lib/python/Products/PythonScripts/patches.py
-=-
Added:
Zope/branches/Zope-2_8-branch/lib/python/Products/PythonScripts/patches.py
===
---
Zope/branches/Zope-2_8-branch/lib/python/Products/PythonScripts/patches.py
(rev 0)
+++
Zope/branches/Zope-2_8-branch/lib/python/Products/PythonScripts/patches.py
2008-08-13 18:08:21 UTC (rev 89809)
@@ -0,0 +1,99 @@
+
+
+
+# Monkey patch for LP #257276 (Hotfix-2008-08-12)
+#
+# This code is taken from the encodings module of Python 2.4.
+# Note that this code is originally (C) CNRI and it is possibly not
compatible
+# with the ZPL and therefore should not live within svn.zope.org. However
this
+# checkin is blessed by Jim Fulton for now. The fix is no longer required
with
+# Python 2.5 and hopefully fixed in Python 2.4.6 release.
+
+
+# Written by Marc-Andre Lemburg ([EMAIL PROTECTED]).
+# (c) Copyright CNRI, All Rights Reserved. NO WARRANTY.
+
+def search_function(encoding):
+
+# Cache lookup
+entry = _cache.get(encoding, _unknown)
+if entry is not _unknown:
+return entry
+
+# Import the module:
+#
+# First try to find an alias for the normalized encoding
+# name and lookup the module using the aliased name, then try to
+# lookup the module using the standard import scheme, i.e. first
+# try in the encodings package, then at top-level.
+#
+norm_encoding = normalize_encoding(encoding)
+aliased_encoding = _aliases.get(norm_encoding) or \
+ _aliases.get(norm_encoding.replace('.', '_'))
+if aliased_encoding is not None:
+modnames = [aliased_encoding,
+norm_encoding]
+else:
+modnames = [norm_encoding]
+for modname in modnames:
+
+if not modname or '.' in modname:
+continue
+
+try:
+mod = __import__(modname,
+ globals(), locals(), _import_tail)
+if not mod.__name__.startswith('encodings.'):
+continue
+
+except ImportError:
+pass
+else:
+break
+else:
+mod = None
+
+try:
+getregentry = mod.getregentry
+except AttributeError:
+# Not a codec module
+mod = None
+
+if mod is None:
+# Cache misses
+_cache[encoding] = None
+return None
+
+# Now ask the module for the registry entry
+entry = tuple(getregentry())
+if len(entry) != 4:
+raise CodecRegistryError,\
+ 'module %s (%s) failed to register' % \
+ (mod.__name__, mod.__file__)
+for obj in entry:
+if not callable(obj):
+raise CodecRegistryError,\
+ 'incompatible codecs in module %s (%s)' % \
+ (mod.__name__, mod.__file__)
+
+# Cache the codec registry entry
+_cache[encoding] = entry
+
+# Register its aliases (without overwriting previously registered
+# aliases)
+try:
+codecaliases = mod.getaliases()
+except AttributeError:
+pass
+else:
+for alias in codecaliases:
+if not _aliases.has_key(alias):
+_aliases[alias] = modname
+
+# Return the registry entry
+return entry
+
+
+import encodings
+encodings.search_function.func_code = search_function.func_code
+
Andreas, did you actually test this patch on 2.8 with Python 2.3? It
relies on a name ('_aliases') which is not present in
lib/python2.3/encodings/__init__.py. E.g.:
$ diff -ru lib/python2.{3,4}/encodings/__init__.py
...
@@ -38,6 +38,7 @@
''
''
'')
+_aliases = aliases.aliases
class CodecRegistryError(exceptions.LookupError,
exceptions.SystemError):
...
Tres.
- --
===
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIpERy+gerLs4ltQ4RArtdAKCmF+0C8Behv50Ke7uI2D1X2WKn6ACfe7/b
cS2R8xHNePOsei9ElD809wA=
=Ex2l
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
[Zope-dev] paula code preview
Hi *, paula's code entered now the collective (https://svn.plone.org/svn/collective/paula/). Central component (currently) for testing is paula.suite, which uses paula.examples for testing. Paula is an authenticator plugin for PAU that uses content objects as authentication and property providers for principals. Interoperation with PAU ist working, the test is in paula.suite.README.txt paula.plonepas a layer for using paula.suite within PlonePAS will follow soon, as well as support for group content. Code reviews/comments are highly welcome. thx florian pgpQRekFYLG1Z.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.app.authentication 3.4.3 + download.zope.org/simple == broken
If you use the http://download.zope.org/ppix or http://download.zope.org/simple indexes and try to get zope.app.authentication 3.4.3 (the newest), you will get a 404 error. Looking at PyPI and the zope.org index, it is evident why. http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists one release, the source release http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3 eggs as well. I strongly suspect that someone uploaded the zope.app.authentication eggs to PyPI; the zope.org index saw them and recorded them; and then someone removed the eggs from PyPI. It would be great if someone could re-upload the eggs to PyPI. More importantly, this is a reminder to please not remove eggs. The behavior or download.zope.org/simple is reasonable. Removing eggs isn't. :-) Thanks Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication 3.4.3 + download.zope.org/simple == broken
Gary Poster a écrit : If you use the http://download.zope.org/ppix or http://download.zope.org/simple indexes and try to get zope.app.authentication 3.4.3 (the newest), you will get a 404 error. Looking at PyPI and the zope.org index, it is evident why. http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists one release, the source release http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3 eggs as well. I strongly suspect that someone uploaded the zope.app.authentication eggs to PyPI; the zope.org index saw them and recorded them; and then someone removed the eggs from PyPI. It would be great if someone could re-upload the eggs to PyPI. More importantly, this is a reminder to please not remove eggs. The behavior or download.zope.org/simple is reasonable. Removing eggs isn't. :-) Indeed... I've reuploaded them but they don't have the same MD5. Is it a problem? easy_install does not seem to complain Thanks Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] paula code preview
On Thu, Aug 14, 2008 at 07:24:16PM +0200, Florian Friesdorf wrote: Hi *, paula's code entered now the collective (https://svn.plone.org/svn/collective/paula/). Central component (currently) for testing is paula.suite, which uses paula.examples for testing. Paula is an authenticator plugin for PAU that uses content objects as authentication and property providers for principals. Interoperation with PAU ist working, the test is in paula.suite.README.txt paula.plonepas a layer for using paula.suite within PlonePAS will follow soon, as well as support for group content. Up-to-date state information is in https://svn.plone.org/svn/collective/paula/STATE.txt. I will keep that file updated... Code reviews/comments are highly welcome. thx florian pgpOlFC8etCkJ.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.app.authentication 3.4.3 + download.zope.org/simple == broken
On Aug 14, 2008, at 4:32 PM, Christophe Combelles wrote: Gary Poster a écrit : If you use the http://download.zope.org/ppix or http://download.zope.org/simple indexes and try to get zope.app.authentication 3.4.3 (the newest), you will get a 404 error. Looking at PyPI and the zope.org index, it is evident why. http://pypi.python.org/pypi/zope.app.authentication/3.4.3 only lists one release, the source release http://download.zope.org/simple/zope.app.authentication/ lists 3.4.3 eggs as well. I strongly suspect that someone uploaded the zope.app.authentication eggs to PyPI; the zope.org index saw them and recorded them; and then someone removed the eggs from PyPI. It would be great if someone could re-upload the eggs to PyPI. More importantly, this is a reminder to please not remove eggs. The behavior or download.zope.org/simple is reasonable. Removing eggs isn't. :-) Indeed... I've reuploaded them but they don't have the same MD5. Is it a problem? I don't know the official answer, but it doesn't seem to be a problem practically for my tests. It works. easy_install does not seem to complain Thank you. Gary ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] KGS buildbot news (zope.server failure almost explained)
Marius Gedminas a écrit : On Sat, Aug 09, 2008 at 01:50:33AM +0300, Marius Gedminas wrote: On Sat, Aug 09, 2008 at 12:57:48AM +0300, Marius Gedminas wrote: - zope.server tests fail horribly with invalid file descriptor errors. I cannot reproduce this error in isolation (bin/test -m zope.server), but I can reproduce it when I run all the tests together. Some previous test is mucking stuff up. 'bin/test -m ZEO -m zope.server' is enough to reproduce this error. Minimal test case: bin/test -pvc1 -m zope.server -t testAPPE -m ZEO -t insane The ZEO test that breaks zope.server.ftp is multiple_storages_invalidation_queue_is_not_insane (ZEO.tests.testZEO) For completeness, the full sequence of steps is check out zope.release branch 3.4 bootstrap and run buildout bin/generate-buildout cd test ../bin/buildout bin/test -pvc1 -m zope.server -t testAPPE -m ZEO -t insane thanks for isolating it, I've found a way to prevent the failure to occur! The real problem comes from the ZEO tests, I've reported it here: https://bugs.launchpad.net/zodb/+bug/257954 The final explanation is that the testrunner imports every test modules. Some tests modules located in zope.server and zope.app.server also import zope.server.dualmodechannel, which creates a pipe (a global trigger). One of the ZEO tests close this pipe although it shouldn't. When the zope.server tests happen, the pipe is already closed and the tests fail. Now, We need to: --- - release a bugfix version of zope.server 3.4.3 - release a bugfix version of zope.app.server 3.4.2 - fix z3c.formdemo and z3c.formjs against z3c.form 1.8.2 (This should be straightforward) We can also: - release a bugfix version of zope.publisher 3.4.4 that fixes an old critical bug ( https://bugs.launchpad.net/zope3/+bug/98440 ) - release a bugfix version of zc.zope3recipes 0.6.2, which fixes some problem with unwanted upgrades during tests. (although this is not needed for the sandboxed tests of KGS in the buildbot to pass) We should probably: --- - wait for setuptools 0.6c9 that fixes a major problem with subversion 1.5 - wait for the final ZODB 3.8.1. It would be good to include some fix for LP 257954 After that we are ready for a release of zope 3.4. We should also probably consider waiting a bit more for the new site (new.zope.org) to come up, but I don't know when it will be finished. It only needs some content for zope2, grok, and some other pages. Christophe Marius Gedminas ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
