Re: [Zope-dev] zope-tests - FAILED: 17, OK: 91
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-May/041834.html
[2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64
https://mail.zope.org/pipermail/zope-tests/2011-May/041836.html
Still the I-can't-reproduce-atexit-segfault: can *anybody* except this
buildbot reproduce the issue? What Python 2.7 version is the buildbot
running, and how was it built?
[3]FAILED Zope Buildbot / zopetoolkit-1.0-py2.5 slave-osx
https://mail.zope.org/pipermail/zope-tests/2011-May/041867.html
The is an FTP test failure, similar to others which have showed up::
- -- $ -
Failure in test testHELP (zope.server.ftp.tests.test_ftpserver.Tests)
Traceback (most recent call last):
File
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
line 260, in run
testMethod()
File
/Users/buildslave/.buildout/eggs/zope.server-3.6.2-py2.5.egg/zope/server/ftp/tests/test_ftpserver.py,
line 278, in testHELP
self.assertEqual(self.execute('HELP', 1), result)
File
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/unittest.py,
line 334, in failUnlessEqual
(msg or '%r != %r' % (first, second))
AssertionError: '214-The following commands are recognized\r\n' !=
'214-The following commands are recognized\r\nHelp goes here
somewhen.\r\n214 Help done.\r\n'
- -- $ -
I have no idea why this failure is only occasionaly, and only on OS/X.
[4]FAILED Zope Buildbot / zopetoolkit_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-May/041857.html
Oddball build failure::
- -- $ -
remoteFailed: [Failure instance: Traceback (failure with no frames):
class 'twisted.internet.error.ConnectionLost': Connection to the other
side was lost in a non-clean fashion.
- -- $ -
[5]FAILED Zope Buildbot / zopetoolkit_win-py2.6 slave-win
https://mail.zope.org/pipermail/zope-tests/2011-May/041856.html
Ditto.
[13] FAILED winbot / ztk_dev py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041891.html
[14] FAILED winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041892.html
[15] FAILED winbot / ztk_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041894.html
[16] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041895.html
[17] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041897.html
These are all the same bug::
- -- $ -
Error in test testNoTargetLanguage
(zope.app.i18n.tests.test_translationdomain.TestTranslationDomain)
Traceback (most recent call last):
File c:\Python27_64\lib\unittest\case.py, line 318, in run
testMethod()
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.i18n\src\zope\i18n\tests\test_itranslationdomain.py,
line 99, in testNoTargetLanguage
eq(translate('short_greeting', context=context, default=42), 42)
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.app.i18n\src\zope\app\i18n\translationdomain.py,
line 74, in translate
catalog_names = self._catalogs.get(target_language, [])
TypeError: Object has default comparison
- -- $ -
WTF? We have tests for zope.i18n which pull in code from zope.app.i18n?
Not only that, but we have an error being raised from the OOBTree
changes Jim landed in October, in a code base which hasn't changed since
March.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3dAbYACgkQ+gerLs4ltQ6n9wCbB9VXSzcYzm9qpQZ9KHPW+Yk8
R5wAoIpSKJOD2bRCcogzcOmIOlZzfMz/
=dLYh
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 17, OK: 91
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[13] FAILED winbot / ztk_dev py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041891.html
[14] FAILED winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041892.html
[15] FAILED winbot / ztk_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041894.html
[16] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041895.html
[17] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041897.html
These are all the same bug::
-- $ -
Error in test testNoTargetLanguage
(zope.app.i18n.tests.test_translationdomain.TestTranslationDomain)
Traceback (most recent call last):
File c:\Python27_64\lib\unittest\case.py, line 318, in run
testMethod()
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.i18n\src\zope\i18n\tests\test_itranslationdomain.py,
line 99, in testNoTargetLanguage
eq(translate('short_greeting', context=context, default=42), 42)
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.app.i18n\src\zope\app\i18n\translationdomain.py,
line 74, in translate
catalog_names = self._catalogs.get(target_language, [])
TypeError: Object has default comparison
-- $ -
WTF? We have tests for zope.i18n which pull in code from zope.app.i18n?
Not only that, but we have an error being raised from the OOBTree
changes Jim landed in October, in a code base which hasn't changed since
March.
We definitely have some kind of failed cleanup going on here: the
standalone buildout for zope.i18n does *not* pull in zope.app.i18n, and
the tests all pass without it.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3dBHYACgkQ+gerLs4ltQ50ogCeLxr+nWgvyCDAcOq5hwn7lpFF
x7YAn07BlqEGF5pz/KlbuS+49k8BTn/G
=hLii
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 17, OK: 91
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/25/2011 09:30 AM, Tres Seaver wrote:
[13] FAILED winbot / ztk_dev py_254_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041891.html
[14] FAILED winbot / ztk_dev py_265_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041892.html
[15] FAILED winbot / ztk_dev py_265_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041894.html
[16] FAILED winbot / ztk_dev py_270_win32
https://mail.zope.org/pipermail/zope-tests/2011-May/041895.html
[17] FAILED winbot / ztk_dev py_270_win64
https://mail.zope.org/pipermail/zope-tests/2011-May/041897.html
These are all the same bug::
-- $ -
Error in test testNoTargetLanguage
(zope.app.i18n.tests.test_translationdomain.TestTranslationDomain)
Traceback (most recent call last):
File c:\Python27_64\lib\unittest\case.py, line 318, in run
testMethod()
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.i18n\src\zope\i18n\tests\test_itranslationdomain.py,
line 99, in testNoTargetLanguage
eq(translate('short_greeting', context=context, default=42), 42)
File
c:\buildslave\ztk_dev_py_270_win64\build\src\zope.app.i18n\src\zope\app\i18n\translationdomain.py,
line 74, in translate
catalog_names = self._catalogs.get(target_language, [])
TypeError: Object has default comparison
-- $ -
WTF? We have tests for zope.i18n which pull in code from zope.app.i18n?
Not only that, but we have an error being raised from the OOBTree
changes Jim landed in October, in a code base which hasn't changed since
March.
We definitely have some kind of failed cleanup going on here: the
standalone buildout for zope.i18n does *not* pull in zope.app.i18n, and
the tests all pass without it.
Silly wabbit -- I assumed that the traceback stack accurately
reflected the source of the failing test. This failure is actually in
zope.app.i18n's tests, not zope.i18n's (ob. note on the evil of
frameworking out unit tests). However, I cannot reproduce the failure
in a standalone checkout of zope.app.i18n.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3dB/AACgkQ+gerLs4ltQ6AuQCfY2gkcMk2D0tR367tf9rFa6dS
1pIAoIrY08cCem2lfTyZLoCP4pdY6uJP
=ankk
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 18, OK: 79, UNKNOWN: 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [5]UNKNOWN UNKNOWN : Zope-2.12 Python-2.6.6 : Linux https://mail.zope.org/pipermail/zope-tests/2011-May/041640.html This is a PyPI unreachable build failure. [6]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/041648.html [7]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/041650.html The segfault-on-exit which I can't reproduce on ubuntu64. [15] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-May/041691.html [16] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-May/041692.html [17] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-May/041693.html [18] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-May/041694.html [19] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-May/041695.html In each of these, he buildout fails (silently) while trying to check out code from SVN: mr.developer: svn: Can't create tunnel: The system cannot find the file specified. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3agPkACgkQ+gerLs4ltQ4UZACgxi0EhmPVG1KLLOYQRkWIzCcy l6IAmwVACT3MZ5eKGgqjax1l/q+Q5UPP =iZDp -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: zope.server/branches/achapman-exc-info/src/zope/server/http/ further compliance with WSGI PEP.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/17/2011 10:14 AM, Satchidanand Haridas wrote: --- zope.server/branches/achapman-exc-info/src/zope/server/http/wsgihttpserver.py 2011-05-17 12:41:54 UTC (rev 121686) +++ zope.server/branches/achapman-exc-info/src/zope/server/http/wsgihttpserver.py 2011-05-17 14:14:20 UTC (rev 121687) @@ -77,12 +77,16 @@ env = self._constructWSGIEnvironment(task) def start_response(status, headers, exc_info=None): +if task.wroteResponseHeader() and not exc_info: +raise AssertionError(start_response called a second time + without providing exc_info.) if exc_info: try: if task.wroteResponseHeader(): raise exc_info[0], exc_info[1], exc_info[2] else: -pass +# As per WSGI spec existing headers must be cleared +task.accumulated_headers = None finally: exc_info = None # Prepare the headers for output @@ -110,12 +114,16 @@ env['wsgi.handleErrors'] = False def start_response(status, headers, exc_info=None): +if task.wroteResponseHeader() and not exc_info: +raise AssertionError(start_response called a second time + without providing exc_info.) if exc_info: try: if task.wroteResponseHeader(): raise exc_info[0], exc_info[1], exc_info[2] else: -pass +# As per WSGI spec existing headers must be cleared +task.accumulated_headers = None finally: exc_info = None # Prepare the headers for output I think AssertionError is the wrong type of exception here: it has debugging / testing semantics which seem inappropriate. I think we would be better of raising an instance of a WSGI-specific exception type Thanks for the careful testing! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3Sm/gACgkQ+gerLs4ltQ7oVQCfa0vEWPcASmLdO2BDeEzoeI5j eZYAniT/BCbFojmKxjq0did6wXLmmmiG =udSc -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Fwd: Re: SVN: zope.server/branches/achapman-exc-info/src/zope/server/http/ further compliance with WSGI PEP.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: Re: [Zope-dev] SVN: zope.server/branches/achapman-exc-info/src/zope/server/http/ further compliance with WSGI PEP. Date: Tue, 17 May 2011 18:34:14 -0400 From: Tres Seaver tsea...@palladion.com To: Satchidanand Haridas satc...@zope.com On 05/17/2011 06:12 PM, Satchidanand Haridas wrote: The WSGI PEP doesn't specify any WSGI specific exceptions. - The sample CGI example that the PEP provides also raises an AssertionError for this scenario: http://www.python.org/dev/peps/pep-0333/#the-server-gateway-side Also note that Paste's HTTP server (Paster) and CherryPy both raise AssertionErrors for this scenario: - Paste: https://bitbucket.org/ianb/paste/src/4f5cfde87603/paste/httpserver.py#cl-166 - CherryPy: http://www.cherrypy.org/browser/trunk/py2/cherrypy/wsgiserver/__init__.py#L2050 Can you clarify what you meant by a WSGI-specific exception type? I was thinking we would derive a custom exception type, e.g.: class WSGIException(Exception): pass and then raise instances of it. I didn't know that the other servers were raising AssertionError, which still seems like the wrong thing to raise at runtime in a production environment: I guess we can follow their lead in this case. Tres. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3S/EAACgkQ+gerLs4ltQ6tPACgw3ZmjN6WheORNzh61fcafn05 CB0Anim/B6Ccaa4+KLCCyYn9IA7QdADE =bjI7 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 10, OK: 72
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/040775.html [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/040777.html I was unable to reproduce the segfault on my ubuntu64 box: - - % $ uname -srm Linux 2.6.32-31-server x86_64 $ cd /tmp $ svn co svn+ssh://svn.zope.org/repos/main/Zope/trunk ... $ cd trunk $ /opt/Python-2.7.1/bin/python bootstrap.py bin/buildout ... $ bin/alltests ... Running OFS.tests.testCopySupportEvents.EventLayer tests: Set up OFS.tests.testCopySupportEvents.EventLayer in 0.094 seconds. Ran 14 tests with 0 failures and 0 errors in 0.041 seconds. Running OFS.tests.testCopySupportHooks.HookLayer tests: Tear down OFS.tests.testCopySupportEvents.EventLayer in 0.000 seconds. Set up OFS.tests.testCopySupportHooks.HookLayer in 0.092 seconds. Ran 14 tests with 0 failures and 0 errors in 0.044 seconds. Running Testing.ZopeTestCase.layer.ZopeLite tests: Tear down OFS.tests.testCopySupportHooks.HookLayer in 0.000 seconds. Set up Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Ran 218 tests with 0 failures and 0 errors in 3.967 seconds. Running Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer tests: Set up Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.002 seconds. Ran 18 tests with 0 failures and 0 errors in 0.026 seconds. Running Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer tests: Tear down Testing.ZopeTestCase.testZODBCompat.ZODBCompatLayer in 0.001 seconds. Set up Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Ran 2 tests with 0 failures and 0 errors in 0.005 seconds. Running zope.testrunner.layer.UnitTests tests: Tear down Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Ran 2368 tests with 0 failures and 0 errors in 44.260 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. Total: 2634 tests, 0 failures, 0 errors in 49.278 seconds. - - % No segfault. :( Maybe we need to wire in Victor Stinner's 'faulthandler'[1] on the buildbot machine which provokes the segfaults and see what we learn. [1] http://pypi.python.org/pypi/faulthandler/2.0 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3NZIcACgkQ+gerLs4ltQ5TsgCglSVUE+pUuy10YuubPH8/uMyU Ol0AoNsoH9ahtW0A5fW//I/TrmRUNX7L =ckrk -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] AUTHENTICATED_USER
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/13/2011 03:36 PM, Richard Harley wrote: Please could someone tell me why AUTHENTICATED_USER was deprecated in favour of the python security module? A quick google says because it can be replaced..but this isn't really a good in depth explanation? If a request was manipulated to include another AUTHENTICATED_USER, wouldn't Zope just error out anyway? What makes you say that AUTHENTICATED_USER is deprecated? ZPublisher sets and uses the variable in the environment without any deprecations. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3NjKUACgkQ+gerLs4ltQ5RiQCfVWCiOZ7mmfkaZIYLv9JFQsF/ XtEAoJcqmxc9+4YBvzxTP23Sjq8fVhlN =MhRQ -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] zope-tests - FAILED: 10, OK: 66, UNKNOWN: 3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 https://mail.zope.org/pipermail/zope-tests/2011-May/040633.html Looks like an odd buildbot failure, 'twisted.spread.pb.PBConnectionLost'. [2]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-May/040621.html Ditto. [3]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-May/040632.html Ditto. [4]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/040628.html This is the same segfault-on-exit-after-passing-all-tests failure we have beein seeing. [5]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/040631.html Ditto. [6]FAILED Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-May/040634.html Another 'PBConnectionLost', this time while running buildout. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3KebgACgkQ+gerLs4ltQ4WwwCgxrLM2taaszjapkV9GokMBUAI cpwAn0R/QrsQ6kbixC98AIhztHrntYmT =UW04 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Latest Python security fix (2.5.6c1 / 2.6.7rc1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/09/2011 05:28 AM, Hanno Schlichting wrote: Hi. I tried installing Python 2.6.7rc1 and got tons of test failures in Zope/Plone. I didn't have time to look into them in more detail, but they looked zope.testbrowser / mechanize related. I'm assuming the same is true for Python 2.5.6c1. If anyone has time to look into this, it would be great. At least be careful with applying the security hotfix to your Python installations. What branch of Zope? I just downloaded 2.6.7rc1, built and installed it, and was able to bootstrap a fresh Zope2 trunk buildout and run all tests without failure. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3H9bgACgkQ+gerLs4ltQ4c5gCfSqFFxZokt8bdpH5OBDbHsRT1 n3MAnjb+Om/ENfwWMknX4LV6X/t89ARb =CMv6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 71
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/30/2011 01:00 AM, Zope tests summarizer wrote: [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039360.html [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039362.html OK, I looked closer: these failures are happening: - - During the final cleanup phase (all tests pass first); - - Only on ubuntu64; - - Only on Python 2.7. Does that suggest anything to anyone? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk28NrEACgkQ+gerLs4ltQ6jEgCfXo0boOsIpuD2MWw0aZ4aiJ6i Pf0An0lo+Ugo+f0wEDZUegzt0rfS4Lpj =Mfec -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 71
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/30/2011 12:20 PM, Tres Seaver wrote: On 04/30/2011 01:00 AM, Zope tests summarizer wrote: [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039360.html [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039362.html OK, I looked closer: these failures are happening: - During the final cleanup phase (all tests pass first); - Only on ubuntu64; - Only on Python 2.7. Does that suggest anything to anyone? I wonder if we have a bug in Python 2.7 here: I'm seeing deprecation warnings for CObject:: - % - /path/to/z213/eggs/zope.proxy-3.6.1-py2.7-linux-i686.egg/zope/proxy/__init__.py:18: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead. from zope.proxy._zope_proxy_proxy import * /path/to/z213/eggs/ZODB3-3.10.2-py2.7-linux-i686.egg/persistent/__init__.py:19: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead. from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY /path/to/z213/eggs/ExtensionClass-2.13.2-py2.7-linux-i686.egg/ExtensionClass/__init__.py:105: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead. from _ExtensionClass import * /path/to/z213/eggs/Acquisition-2.13.7-py2.7-linux-i686.egg/Acquisition/__init__.py:3: PendingDeprecationWarning: The CObject type is marked Pending Deprecation in Python 2.7. Please use capsule objects instead. from _Acquisition import * - % - and I recall some discussion about issues with the backport of the capsule stuff to 2.7. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk28O0AACgkQ+gerLs4ltQ6BZQCgyLBFxiV/CmwEldPr41ewlaLk nn8AniZf3BvJj4LBFmGmUGU5trU7WR+x =piET -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 11, OK: 92
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED Zope Buildbot / zope2.13-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039211.html [2]FAILED Zope Buildbot / zope2.14-py2.7 slave-ubuntu64 https://mail.zope.org/pipermail/zope-tests/2011-April/039214.html These both look like segfaults:: - % -- Running zope.testing.testrunner.layer.UnitTests tests: Tear down Testing.ZopeTestCase.zopedoctest.testLayerExtraction.TestLayer in 0.001 seconds. Tear down Testing.ZopeTestCase.layer.ZopeLite in 0.000 seconds. Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. process killed by signal 11 program finished with exit code -1 elapsedTime=41.287997 - % -- Anybody know of recent C extension changes which might be responsible? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk25XaQACgkQ+gerLs4ltQ5QxwCfaIWquIblZGvfnTw8hiYnrH5r MnYAoMG/1xY+64Ilwd4kZKHD4KbEompc =Ov/d -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 92, UNKNOWN: 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038665.html [2]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.6 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038676.html These are still failing in the 'svn' step with Directory not empty errors. Jan-Jaap, can you investigate? [3]FAILED Zope Buildbot / zope2.13_win-py2.7 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038648.html This is a weird failure, given that there have been no relevant changes on the Zope 2.13 branch or in AccessControl:: - - % Failure in test test_unauthorized (AccessControl.tests.testZopeGuards.TestGuardedGetattr) Traceback (most recent call last): File C:\Python27\lib\unittest\case.py, line 318, in run testMethod() File c:\users\richard\.buildout\eggs\accesscontrol-2.13.4-py2.7-win32.egg\AccessControl\tests\testZopeGuards.py, line 101, in test_unauthorized self.assertEqual(rc, sys.getrefcount(value)) File C:\Python27\lib\unittest\case.py, line 494, in assertEqual assertion_func(first, second, msg=msg) File C:\Python27\lib\unittest\case.py, line 487, in _baseAssertEqual raise self.failureException(msg) AssertionError: 55464 != 55457 - - % Looking at the code, this seems a highly suspicious result. 55000+ refcounts for the 'args' attribute of a newly-created Method object? Really? [4]FAILED Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038660.html This is also a directory not empty failure, but in the bootstrap phase. Again, this is a THA host. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2xf+cACgkQ+gerLs4ltQ5VQwCeOiAScet6kho/RC22lpQhKRHW yikAnil5GREAvg3TnfMqDaezK+S4sHfy =nXt0 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 14, OK: 74, UNKNOWN: 3
py_270_win32 [17] winbot / ztk_dev py_270_win64 Non-OK results -- [1]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038617.html [2]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.5 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038619.html [3]UNKNOWN UNKNOWN : Zope Buildbot / zopetoolkit_win-py2.6 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038620.html These three all failed in the 'svn' step with a directory not empty error. [4]FAILED Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 https://mail.zope.org/pipermail/zope-tests/2011-April/038571.html Tests of 'zope.testing.testrunner' seem to be failing because 'LAYER FINISHED' is not being emitted in subprocess test runes. [5]FAILED Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/038614.html Another directory not empty error, this time in the bootstrap step. [13] FAILED winbot / ztk_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038623.html [14] FAILED winbot / ztk_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038624.html [15] FAILED winbot / ztk_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038625.html [16] FAILED winbot / ztk_dev py_270_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/038626.html [17] FAILED winbot / ztk_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/038627.html These all seem to be failures in testing dependencies for zope.app.publication:: test-zopeapp-zope.app.publication failed with: Test-module import failures: ''' from zope.testing.cleanup import cleanUp ImportError: No module named testing.cleanup (I see looking down the list that Brian Sutherland thinks he fixed these in r121453). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2wUewACgkQ+gerLs4ltQ70NgCgkYmHFkJy8C/dr78TPrx3Y6Zj 0MgAn35W3/lxBzDq2cvbcnGAcp1APsT5 =HLGP -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Products.ZCatalog/trunk/ Handle `TypeErrors` in the KeywordIndex if an indexed attribute is a method with required arguments.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/21/2011 02:07 PM, Hanno Schlichting wrote: Log message for revision 121454: snip Protect against implicitly acquiring attributes for indexes. snip Modified: Products.ZCatalog/trunk/src/Products/PluginIndexes/common/UnIndex.py === --- Products.ZCatalog/trunk/src/Products/PluginIndexes/common/UnIndex.py 2011-04-21 06:27:40 UTC (rev 121453) +++ Products.ZCatalog/trunk/src/Products/PluginIndexes/common/UnIndex.py 2011-04-21 18:07:09 UTC (rev 121454) @@ -17,6 +17,7 @@ from logging import getLogger import sys +from Acquisition import aq_base from BTrees.IIBTree import intersection from BTrees.IIBTree import IITreeSet from BTrees.IIBTree import IISet @@ -264,6 +265,9 @@ # self.id is the name of the index, which is also the name of the # attribute we're interested in. If the attribute is callable, # we'll do so. +has_attr = getattr(aq_base(obj), attr, _marker) +if has_attr is _marker: +return _marker try: datum = getattr(obj, attr) if safe_callable(datum): This is an API change: it breaks code which deliberately uses acquisition to supply defaults for indexing purposes. There needs to be some way to put it back, at least (maybe a zope.conf setting?) Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2wfuYACgkQ+gerLs4ltQ43UACghtYqQjy4zlpO9h8Jjr1dMBd5 37wAoKTiTYFvLKMtyIkVWDw0SycmfPtr =ptTL -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 76, UNKNOWN: 1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/20/2011 01:00 AM, Zope tests summarizer wrote: [1]UNKNOWN UNKNOWN : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 https://mail.zope.org/pipermail/zope-tests/2011-April/038523.html This is an error in the bootstrap phase: Traceback (most recent call last): Failure: twisted.spread.pb.PBConnectionLost: [Failure instance: Traceback (failure with no frames): class 'twisted.internet.error.ConnectionDone': Connection was closed cleanly. ] Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2u8VoACgkQ+gerLs4ltQ47PACgyR7GC7OtH8gggukcxLIqRoLL H40An2L/NmRb1z5dX6KhO5DPoxzfejfM =4L9C -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope2] Multiline response headers causing problems for proxies.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/18/2011 12:01 PM, Laurence Rowe wrote: When using response.appendHeader, Zope appends the new value following an ,\r\n\t which splits the header over multiple lines. While this behaviour is standards compliant, it causes problems for both Varnish [1] and Nginx [2] which may then mangle the header value. In fact the HTTP 1.0 spec notes that splitting over multiple lines in not recommended [3], though the HTTP 1.1 spec does not mention this explicitly, though it does say [4]: Applications ought to follow common form, where one is known or indicated, when generating HTTP constructs, since there might exist some implementations that fail to accept anything Are there any objections to me applying the attached patch to Zope 2.13 and trunk? +0. We likely need to test that your patch doesn't break stuff on other maybe-not-compliant servers (older Apache, IIS). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2shMUACgkQ+gerLs4ltQ4oKgCg0/BXLTh3VvpBGeNgc+WFKx9V UdEAnRp1lxbXDKFbrJ8nBwgWaRJ/B0y1 =xjg8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] CatalogPathAwareness and zope.lifecycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/16/2011 11:55 AM, Sascha Welter wrote: (Fri, Apr 15, 2011 at 02:39:26PM +0200) Hanno Schlichting wrote/schrieb/egrapse: I assume this kind of thing has been discussed and the decision has been taken on judging backwards compatibility vs. the benefits of doing this? The particular code was unused for several years, Sigh. Sorry Hanno, but just *sigh*. Unused? Unused by whom? There is code out there that uses stuff without you or anybody else typing in the code on a keyboard. How can you claim it's unused? Do you make audits on what pieces of code people use in their Zope projects? People want to be able to move an existing Zope app to a new server and a new Zope install there without having to sell the customer onto 15 hours of maintenance coding to fix 100 things that break. Not every project is a new project. using manage_* methods is deprecated since Zope 2.8 or 2.9. You are wrong. CHANGES.txt in Zope 2.11 does not know anything about manage_* being deprecated. Instead it says: - Turned deprecation warnings for manage_afterAdd, manage_beforeDelete and manage_afterClone methods into discouraged warnings. These methods will not be removed in Zope 2.11, but stay for the foreseeable future. Using events is still highly encouraged. The CHANGES.txt from 2.12 says: Downgrade the ``manage_* is discouraged. You should use event subscribers instead`` warnings to debug level logging. This particular warning hasn’t motivated anyone to actually change any code. And it will damn sure not motivate anybody, because code that uses that runs just fine (thank you) and nobody sees any need to fix it to use something that is undocumented and not tested in that particular setup. That's not how maintenance on a working system works. CHANGES.txt in 2.13 doesn't know anything about manage_* being deprecated or removed any further. If it doesn't break anything, if it doesn't break new code, why depreciate and why remove it? We've had this same game with zLOG and manage_afterAdd before. They're both still here, for good reason. If you really need this code, just copy it from an old release into your own codebase. How about you don't delete it and I don't have to add it back? Less work for you, less work for me, less work for everybody. Developing with Zope 2 is probably a frustrating experience, but that shouldn't come as a surprise to anyone. It comes as a surprise to me. In fact, I find developing with Zope 2 quite an amusing and entertaining experience. And easy. You must be doing something wrong. I can understand though that Zope is not a system for newbies to start *right now*, OK. The project is dead for several years now and is only kept left alive while Plone is migrating away from it or some long time developers are still using it. It's a large piece of legacy code that has no future - certainly not for new users or developers not already familiar with it. Well, I don't know anything about what Plone is or isn't doing. No Plone was ever able to move to a different Zope version without rewriting basically everything, so maybe you think that's normal. It isn't like that for most everybody else though. IMHO the way to treat a large piece of legacy code is *not* to break various things inside it because some other idea to do things seemed so much cooler a while back (but which we also abandoned, because we'll get rid of it all anyway). The way to do that properly is to make it as stable an lasting as you can and let it stay alive till it falls over by itself. So if you think it's dead, OK, but there is no reason to actively kill it piece by piece. Moving a big old application across multiple major versions at onece of any platform is likely to be painful: even projects which are careful about backward compatibility (Zope has historically been very good at this) will have issued deprecation warnings in the versions you skip. Your best bet would be to port the app stepwise to the latest release of each major version, noting and fixing the warnings as you go. Zope 2.12 - 2.13 is likely to be the biggest jump, because 2.13 includes lots of changes which *remove* functionality from Zope to optional add-ons. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2qyo8ACgkQ+gerLs4ltQ4LxgCeMDpTlyI21tcIOSnyIthn55Qs cWIAn1AAOfjk4+OOjrX1phVRk2dxF51f =67vM -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists
Re: [Zope-dev] CatalogPathAwareness and zope.lifecycle
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/17/2011 10:08 AM, Sascha Welter wrote: (Sun, Apr 17, 2011 at 07:10:07AM -0400) Tres Seaver wrote/schrieb/egrapse: Moving a big old application across multiple major versions at onece of any platform is likely to be painful: Tres, I know how to move an app to newer zope versions. My apps are enough well behaved to have survived since 2.7 with few changes and from 2.10 straight to 2.13 needed only very few adjustments so far. What I want to know: The term CatalogPathAwareness was not found in the archives of zope-dev in the last 6 years or so. Can any zope developer deprecate or remove things on their own without discussion? Code talks. Hanno deprecated the CPA base class in r115308 in August 2010 with the comment: Fully deprecate both CatalogAwareness and CatalogPathAwareness. They are untested and unused. Event subscribers for zope.lifecycleevents are the way to go. Note that this was in the midst of a set of *huge* improveements to the catalog (the query plan stuff), for which we should be very grateful: such improvements grant legitimacy to Hanno's judgement about the state of the code. Note that if you need time to finish revising code which depends on the deprecated components, you can pin Products.ZCatalog=2.13.99 until your code is ready: that is one of the beauties of moving the code into a separately-released distribution. Removing CatalogAware/CatalogPathAware from Products.ZCatalog is one point in question. Removing manage_afterAdd et al is another. This will break lots of code out there that would happily run on otherwise. 'manage_afterAdd' and siblings have been deprecated for a *long* time (since Zope 2.9.0b1, 2005-12-06): http://svn.zope.org/Zope/tags/2.9.0b1/doc/CHANGES.txt?rev=40603view=markup Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2rFogACgkQ+gerLs4ltQ78KQCgoEuO3hUUt4rokZ5qndyaRx1H sZIAnjrRVwoQQmW1ncBoPO1/eN10M8rw =AvWq -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: persistent/trunk/ include all test dependencies
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/14/2011 12:29 AM, David Glick wrote: Log message for revision 121421: include all test dependencies Changed: U persistent/trunk/buildout.cfg U persistent/trunk/setup.py -=- Modified: persistent/trunk/buildout.cfg === --- persistent/trunk/buildout.cfg 2011-04-14 04:20:08 UTC (rev 121420) +++ persistent/trunk/buildout.cfg 2011-04-14 04:29:37 UTC (rev 121421) @@ -7,7 +7,7 @@ [test] recipe = zc.recipe.testrunner eggs = -persistent +persistent [test] [scripts] recipe = zc.recipe.egg Modified: persistent/trunk/setup.py === --- persistent/trunk/setup.py 2011-04-14 04:20:08 UTC (rev 121420) +++ persistent/trunk/setup.py 2011-04-14 04:29:37 UTC (rev 121421) @@ -24,9 +24,11 @@ from setuptools import setup TESTS_REQUIRE = [ +'transaction', 'zope.interface', 'zope.testing=3.7.0', 'zope.testrunner', +'ZODB3', ] This change serves an anti-goal for the standalone 'persistent' package. I want to rip out (and replace, if needed) any tests which use ZODB, so having them error out because it is missing is a win. 'transaction' shouldn't be needed, either. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2ntdsACgkQ+gerLs4ltQ6ARgCgnQG7AYdt6bzjAFzh2OaG2C+d Up8AoNotgiLnZyOVdV67ySgsw7iQWKPV =87hm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 10, OK: 82, UNKNOWN: 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/13/2011 01:00 AM, Zope tests summarizer wrote: [1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.5 : Linux https://mail.zope.org/pipermail/zope-tests/2011-April/037949.html [2]UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux https://mail.zope.org/pipermail/zope-tests/2011-April/037950.html I presume that these are transient network / index server failures during bootstrap. [3]FAILED winbot / ZODB_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037967.html [4]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037968.html [5]FAILED winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/037884.html Hmm, these look like the Windows vs. Posix rounding error Jim thought he normalized away yesterday. Tres - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2lsa8ACgkQ+gerLs4ltQ77ZQCgkec40RYx0QCn08BVjFhGD5Jx gMgAn1G/LgvTPBuRUKfG7uqlz/Qj0eX/ =0ztM -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 10, OK: 79
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [1]FAILED winbot / ZODB_dev py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037879.html [2]FAILED winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037880.html I'm assuming these failures are due to Jim's recent tinkering with the ZEO cache stuff: Failure in test cache_trace_analysis (ZEO.tests.test_cache) There are also various warnings in red text about versions and large objects on the first run, but not the second. [10] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/037840.html I couldn't reproduce this one in a fresh checkout: the 0.9.10 version of testtools fixes the installation problem with 0.9.9. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2klQMACgkQ+gerLs4ltQ70PACfV6sMGbv9hD3mC9Q4AXTivq4H QvIAnREcnYPkeTInrlskge/ZUgXfW5cK =Oe1Z -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72, UNKNOWN: 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/11/2011 02:57 AM, Michael Howitz wrote: [10] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/037643.html This is also a build failure: - --- % - An error occurred when trying to install testtools 0.9.9. Look above this message for any errors that were output by easy_install. error: c:\temp\easy_install-nalecc\testtools-0.9.9\doc/overview.rst: No such file or directory While: Installing test. Getting distribution for 'testtools'. Error: Couldn't install: testtools 0.9.9 - --- % - The 0.9.9 release of testtools is broken. I contacted the author to re-releases an installable version. I reported a bug on Launchpad: https://bugs.launchpad.net/testtools/+bug/757439 and pushed a branch adding a fix. https://code.launchpad.net/~tseaver/testtools/fix-lp757439 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2i6lcACgkQ+gerLs4ltQ6NbgCgq8FGnzUbBLCIw0A/cxXapVMF Px0An35NR0g7lyW5RV4Johyr3EECSprs =vxcV -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72, UNKNOWN: 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/11/2011 07:47 AM, Tres Seaver wrote: I reported a bug on Launchpad: https://bugs.launchpad.net/testtools/+bug/757439 and pushed a branch adding a fix. https://code.launchpad.net/~tseaver/testtools/fix-lp757439 BTW, for those keeping score at home :), this bug should be chalked up to the MANIFEST.in is a DRY violation column: if the author had used the appropriate VCS plugin for setuptools, instead of MANIFEST.in, the release would have worked fine. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2i6+MACgkQ+gerLs4ltQ4jmwCg0SpyvX+VJlJz8FzsRtB6/FBi BhYAn2hWCXABvZJzlBuua5L2UOJcv5ZF =pxvC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 9, OK: 72, UNKNOWN: 2
:: - --- % - Downloading http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg Traceback (most recent call last): ... File /tmp/tmp7yXBqX/setuptools-0.6c11-py2.6.egg/setuptools/command/easy_install.py, line 919, in run_setup File /tmp/tmp7yXBqX/setuptools-0.6c11-py2.6.egg/setuptools/sandbox.py, line 52, in run_setup AttributeError: 'module' object has no attribute '__getstate__' An error occurred when trying to install zc.buildout. Look above this message for any errors that were output by easy_install. Running ./bin/buildout /bin/sh: ./bin/buildout: No such file or directory - --- % - [10] FAILED winbot / zope.testrunner_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-April/037643.html This is also a build failure: - --- % - An error occurred when trying to install testtools 0.9.9. Look above this message for any errors that were output by easy_install. error: c:\temp\easy_install-nalecc\testtools-0.9.9\doc/overview.rst: No such file or directory While: Installing test. Getting distribution for 'testtools'. Error: Couldn't install: testtools 0.9.9 - --- % - [11] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037671.html This one looks like we might need a backport of a testing-only bugfix from the zope.dublincore trunk: - --- % - File c:\eggs\zope.dublincore-3.7.0-py2.5.egg\zope\dublincore\tests\timeannotators.txt, line 53, in timeannotators.txt Failed example: content.created Expected: datetime.datetime(DATETIME, tzinfo=UTC) Got: datetime.datetime(2011, 4, 9, 20, 50, 36, tzinfo=UTC) - --- % - That fix, released with version 3.8.2, was described as: - --- % - 3.8.2 (2010-02-19) == - - Updated DATETIME regex normalizer to guard against test failure when a datetime's microseconds value is zero. - --- % - Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2iD9gACgkQ+gerLs4ltQ58bgCgqrp43ho8pk0IVqi2M4MytnYo oOcAnAyBkvEvoJGs7E9/ka20hwUYpPTp =9OAh -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 8, OK: 86, UNKNOWN: 4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/06/2011 01:00 AM, Zope tests summarizer wrote: [1]UNKNOWN UNKNOWN : Zope-trunk Python-2.6.5 : Linux https://mail.zope.org/pipermail/zope-tests/2011-April/037287.html [2]UNKNOWN UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux https://mail.zope.org/pipermail/zope-tests/2011-April/037288.html Both of these blow up tryiing to install 'argparse==1.2.1' (I don't know why). That release is not uploaded to PyPI, nor is it in the download.zope.org index. [3]UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-April/037312.html [4]UNKNOWN UNKNOWN : winbot / ZODB_dev py_265_win64 https://mail.zope.org/pipermail/zope-tests/2011-April/037313.html Both of these are failures due to 'client disconnected' errors in ZEO tests. I have no clue about them. [5]FAILED Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win https://mail.zope.org/pipermail/zope-tests/2011-April/037266.html This one looks like a timeout during some part of the buildout step: remoteFailed: [Failure instance: Traceback (failure with no frames): class 'twisted.internet.error.ConnectionLost': Connection to the other side was lost in a non-clean fashion. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2cVpAACgkQ+gerLs4ltQ6EwwCgzVxdBQIijHvfpQzMpyioapAD ovsAoJVkCa6TzLaak/R9v6RhoU10NNka =wXQa -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] CSRF protection for z3c.form
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/04/2011 12:23 PM, Wichert Akkerman wrote: On 2011-4-4 18:22, Roger wrote: Hi Laurence, Stephan Just because you can write login forms with z3c.form this package has nothing to do with authentication. That's just a form framework! Authentication is defently not a part of our z3c.form framework and should not become one. Why do you think authentication has something to do with the z3c.form library? Did I miss something? CSRF has nothing to do with authentication. It has to do with securing forms on websites. Imagine that Alice Malice runs a site she tempts Bob Slob to visit while Bob is logged into your site with privileged credentials. Alice adds javascript to an apparently harmless page which spoofs submitting a form to your site on Bob's behalf, perhaps granting Alice extra permissions, or defacing your site. If your site uses CSRF-protected forms, then real forms will contain hidden field whose value is a signature (a hashed value known only to the server). The server generates the hash when it renders the form, and stores it in the authenticated user's session; when the form is submitted, the server checks that the hash is valid before processing the form. Because it has either a missing or an invalid hash, Alice's spoofed submission can be rejected. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Z9XEACgkQ+gerLs4ltQ60XgCfdsFHMrONDJfLzk/1BNN+ovN9 1ksAn0zWEAnaod3Y3oDlvkCybds1ZMNA =2/zr -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 123 OK, 14 Failed, 3 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win From: jdriessen at thehealthagency.com Date: Thu Mar 31 19:48:31 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036774.html Subject: UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Thu Mar 31 20:02:29 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036777.html Subject: UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Thu Mar 31 20:15:26 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036780.html These are all puzzling: the second test step (the 'test-zopeapp' step) fails with:: - - % --- command timed out: 300 seconds without output, killing pid 3828 SIGKILL failed to kill process using fake rc=-1 program finished with exit code -1 remoteFailed: [Failure instance: Traceback from remote host -- Traceback (most recent call last): Failure: buildbot.slave.commands.TimeoutError: SIGKILL failed to kill process - - % --- Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2VzdoACgkQ+gerLs4ltQ60BgCcCGumPMvb4BkUuv4PPclnCjFn WQ0An2IpYFJttQJXQHEAXYpdXapjb53O =Rm6a -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 78 OK, 10 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2011 06:57 AM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Wed Mar 30 11:00:00 2011 UTC to Thu Mar 31 11:00:00 2011 UTC. There were 88 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 23 from buildbot at winbot.zope.org, 8 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036655.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:27:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036656.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036657.html Subject: FAILED : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036658.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Mar 30 17:28:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036659.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:01:41 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/03.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 21:27:07 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036668.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Wed Mar 30 22:32:38 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036674.html Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 22:43:08 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036675.html Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 30 23:17:23 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036676.html Woohoo! the ZTK and Zope2 buildbots are green! Now if we can just get the rest there. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UdQkACgkQ+gerLs4ltQ7ZmwCgsJ1Yha6GI8gE2Tp6BW8YdPMT //AAoJnJcR518Ec0BJvHsjw3KUlyAAUN =LNUV -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 74 OK, 19 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/30/2011 07:43 PM, Marius Gedminas wrote: On Wed, Mar 30, 2011 at 12:57:54PM +0200, Zope Tests Summarizer wrote: Test failures - Subject: FAILED : Zope 3.4 Known Good Set / py2.4-64bit-linux From: buildbot at pov.lt Date: Tue Mar 29 21:01:43 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036574.html Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Tue Mar 29 21:27:19 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036575.html Subject: FAILED : Zope 3.4 Known Good Set / py2.5-32bit-linux From: buildbot at pov.lt Date: Tue Mar 29 22:29:28 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036581.html So, it's been a week, and the SourceForge bug [1] is still not fixed. [1] http://sourceforge.net/apps/trac/sourceforge/ticket/18486 There are three other possible workarounds: 1. Put ClientForm and mechanize into the buildout cache on the build slave, so buildout doesn't try to go look for newer versions elsewhere. This ought to work: one of the four builders is still green, for this reason. 2. Add an allow-hosts option to buildout.cfg -- except it's generated by a tool I'm not familiar with (zope.kgs.buildout). Maybe I could tweak ~/.pydistutils.cfg on the buildslave? 3. Update versions.cfg in the KGS 3.4 to require a newer setuptools version or distribute, then release it as KGS 3.4.2a1. Except the only setuptools version with the fix is a prerelease (0.6c12dev-r88975). I don't like (1) and (2) because they're local fixes: any user trying to actually use the 3.4 KGS will trip on this problem. In that sense it's useful to have these buildbots red: we know the problem is not fixed yet for the users (assuming the 3.4 KGS still has any). I don't like (3) because, ick, pinning a svn snapshot version? Not cool. It looks like the 'generate-buildout' script from zope.kgs uses a static 'buildout.cfg.in' template. The following patch should do to add 'allow-hosts':: - -- % -- - --- src/zope/kgs/buildout.cfg.in (revision 121173) +++ src/zope/kgs/buildout.cfg.in(working copy) @@ -1,6 +1,9 @@ [buildout] parts = test versions = versions +allow-hosts = +pypi.python.org +*.zope.org [test] recipe = zc.recipe.testrunner - -- % -- Stephan, does that look OK to you? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2UdqIACgkQ+gerLs4ltQ54UgCgn0JBa3b68wnDV0HDb8wOBiuU ldAAn1XC/7bqa21sg3urR2tRSh0q2jun =vaQl -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 74 OK, 19 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/30/2011 06:57 AM, Zope Tests Summarizer wrote: Subject: FAILED : winbot / ztk_dev py_270_win64 From: buildbot at winbot.zope.org Date: Tue Mar 29 16:41:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036536.html Weird buildout failure: c:\buildslave\ztk_dev_py_270_win64\buildbin\buildout.exe -c development.cfg The system cannot find the path specified. Subject: FAILED : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Tue Mar 29 16:42:12 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036537.html Subject: FAILED : winbot / ztk_10 py_265_win32 From: buildbot at winbot.zope.org Date: Tue Mar 29 16:42:59 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036538.html Subject: FAILED : winbot / ztk_10 py_265_win64 From: buildbot at winbot.zope.org Date: Tue Mar 29 16:43:53 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036539.html These all look to be (likely transient) network failures during bootstrapping. Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:09:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036550.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:09:10 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036551.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:28:19 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036558.html Bootstrap failures: I'm hopeful that Jan-Wilbrand has resolved these for tomorrow's run. Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 30 03:56:37 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036594.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 30 04:28:40 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036595.html Ditto. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2TEVUACgkQ+gerLs4ltQ4CiQCePetdFFqqzMXZunyAiiLLP/d8 PBsAnjPz8n2ZxCqnjWGP4qPo0fwIaAiU =0Ezz -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 74 OK, 19 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/30/2011 08:55 AM, Jan-Wijbrand Kolman wrote: On 3/30/11 13:17 PM, Tres Seaver wrote: Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:09:03 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036550.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:09:10 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036551.html Both pending a test run. Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Tue Mar 29 17:28:19 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036558.html Bootstrap failures: I'm hopeful that Jan-Wilbrand has resolved these for tomorrow's run. Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 30 03:56:37 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036594.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 30 04:28:40 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036595.html Ditto. The zopetoolkit-1.0 tests are green now. Excellent -- thank you very much! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2TYCgACgkQ+gerLs4ltQ7KcwCgkOnQDNb4IH91/TXinOwhUquo ZSYAn3eBoGlThRfDeO2IO4nfBm12818o =ET/r -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 74 OK, 14 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Mar 28 15:18:14 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036429.html Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 28 16:46:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036443.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 28 16:47:05 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036444.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Mon Mar 28 17:06:20 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036453.html These four are still dying in the bootstrap step, without any kind of useful output. I just tried to reproduce one without success:: - --- % -- $ cd /tmp $ svn co http://svn.zope.org/repos/main/zopetoolkit/branches/1.0 A1.0/LICENSE.txt A1.0/development.cfg A1.0/zopeapp-versions.cfg A1.0/bootstrap.py A1.0/buildout.cfg A1.0/COPYRIGHT.txt A1.0/ztk.cfg A1.0/README.txt A1.0/zopeapp.cfg A1.0/ztk-versions.cfg A1.0/index.rst U 1.0 Checked out revision 121155. $ cd 1.0/ $ /opt/Python-2.6.5/bin/python bootstrap.py Creating directory '/tmp/1.0/bin'. Creating directory '/tmp/1.0/parts'. Creating directory '/tmp/1.0/eggs'. Creating directory '/tmp/1.0/develop-eggs'. Generated script '/tmp/1.0/bin/buildout'. - --- % -- Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2R6zUACgkQ+gerLs4ltQ7w0QCfZ/jXytAG9yNbu8Zw23gyingt rYAAoM9jxNwqru2WK7cjYcEHw+oRKkwB =qWYz -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 75 OK, 15 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Mar 27 16:12:56 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036349.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Mar 27 16:13:02 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036350.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Mar 27 16:32:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036358.html I am getting 504s when trying to view thses reports. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2QfCUACgkQ+gerLs4ltQ41ngCdF+uDsJfSLmdMEUE4vddUg0p0 8TwAnA7e/Fp9OIcOq6qBz6gwMGnH/5dE =tav+ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Test fixture concepts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/28/2011 10:04 AM, Jim Fulton wrote:
On Sun, Mar 27, 2011 at 11:13 AM, Martin Aspeli
optilude+li...@gmail.com wrote:
Hi,
On 27 March 2011 15:54, Uli Fouquet u...@gnufix.de wrote:
The (limited) experiences with py.test, however, were awesome. Some
points that are quite cool IMHO:
- Easy finding of tests: just write some ``test_function`` in a
``test_module`` and it will be found and executed. That also makes
py.test tests more readable and maybe more intuitive.
I'm not sure this is always a good idea. It feels a bit implicit, and
having a base class isn't really a big problem, IMHO. It seems a bit
like the kind of thing that sounds cool (look, it's even easier!), but
in practice makes little difference.
+1
+1
+1
This is especially important for doctests (and manuel) or any
situation where setup is important and where you can't really guess.
- py.test is more widespread in the Python community (that's my
impression; I can't proof it)
What about nose?
It looks to me like a layerish mechanism might be possible in nose, or
at least like
zope.testing layers could be integrated with nose.
- Support of unittest/unittest2: you can write standard lib setups
(defining TestCases; no need to also write testsuite-setup stuff) and
they will be found/executed. zope.testrunner for instance does not
support the new `setUpClass`/`tearDownClass` concept of unittest2
(yes, you would use layers in that case; but it might be nice if
zope.testrunner would support also class-wide fixtures in
unittest2-style; people from other worlds might expect that to work).
zope.testing should definitely gain support for the new unittest2
hooks. That wouldn't be very hard, though. ;-)
I assume you mean zope.testrunner.
Main drawbacks I see on py.test side are:
- Lack of layer support (yet). Maybe we can do something about that in
`zope.pytest` based on `plone.testing.layer`.
- Limited doctest support. It is quite difficult (AFAIK) to define
fixtures for doctests or to even set the usual doctest options
(``ELLIPSIS``, ``NORMALIZE_WHITESPACE``, ...) at setup time. Doctests
are simply collected and executed and not much finetuning is possible.
With zope.testrunner, you *do* need a test_suite method to run
doctests. I think that's a good thing. Look at plone.testing's README
for examples.
Again, +1
If I were to use nose or py.tests, I would want to adopt an explicit
style, which I believe is possible w nose.
FWIW, I thought the same, but haven't missed 'test_suite' appreciably
after a week or so of acclimatization to the nose discovery mechanism.
The only wrinkle I know of is that one doesn't use base classes for test
cases where the base class itself derives from unittest.TestCase:
instead, the base is just used as a pure mixin.
FWIW, I think we should stop using .txt doctests for unit tests.
I disagree, of course.
Doctests should be used to test *documentation* (the examples are
valid).
Manuel is *much* better for that. (Of course, manuel is arguably a form of
doctest.)
The Sphinx doctest integration[1] ('make doctest') supports both classic
interpreter prompt doctests and a more useful (IMHO) code-output
form, such as:
.. testcode::
1+1# this will give no output!
print 2+2 # this will give output
.. testoutput::
4
[1] http://sphinx.pocoo.org/ext/doctest.html
For actual unit tests, writing tests in a unittest class is
almost always better in the long run. doctests don't scale well and
discourage the kind of ad-hoc this seems broken, I'll just write a
quick test or I just fixed a bug, better add a regression test
testing.
You're just not using them correctly. :)
The vast majority of the doctest testcases in zope.* packages fall into
this category: poor isolation, lots of edge cases which would obscure
any real narrative docs, of which there are almost none. I believe the
conflict is intrinsic, here, and not just an accident of careless /
naive implementation: exercising all the preconditions of the contract
of the function-under-test makes for really poor documentation, but is
essential to good testing.
One thing I hate about unittest is the javiotic ceremony it involves.
Doctests can cut down on the clutter a lot. I believe that that is
py.test's strength as well..
I'll take explicit for $1000, Alex.
More generally, I'd love to see us adopt another test runner so that
we can stop maintianing zope.testrunner. When it was written at
the turn of the century, there weren't good alternatives. Personally,
I think maintaining it is boring.
Nose and coverage have been pretty good to repoze.* and pyramid_*.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE
Re: [Zope-dev] Test fixture concepts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/28/2011 10:56 AM, Wolfgang Schnerring wrote: Hello, * Jim Fulton j...@zope.com [2011-03-28 10:04]: More generally, I'd love to see us adopt another test runner so that we can stop maintianing zope.testrunner. When it was written at the turn of the century, there weren't good alternatives. Personally, I think maintaining it is boring. I agree, it would be nice to get out of the test runner business, just as we're getting out of the networking business more and more courtesy of WSGI. But I'm wary of throwing out the baby with the bathwater, zope.testrunner has quite a few features under the hood that are really useful, which I'm not sure other test runners have, and I definitely wouldn't want to lose. Layers are the most prominent, of course, but then there's post-mortem debugging (-D), coverage integration, ... the list goes on for a few more items, I'm certain. I guess, apart from the layer issue (see other messages in this thread), some research and write-up would be a good idea to get a feeling what the other test runners are like and how they measure up against zope.testrunner. A quick google search turns up nothing appropriate, so I might do a comparison of zope.testrunner, py.test and nose, but that's going to take a while. nose supports post-mortem debugging, and integrates nicely with Net Batchelder's 'coverage' tool. It's extension interface uses setuptools entry points, and is reasonably well documented: http://somethingaboutorange.com/mrl/projects/nose/1.0.0/plugins/writing.html Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2QrXIACgkQ+gerLs4ltQ4SgwCfRXRljDcSF+4jh6f8Qr5Lk/gX EHwAoKsM2w8vIKG7hOriFYXQnViEt8RI =6G8m -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 87 OK, 18 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/27/2011 06:57 AM, Zope Tests Summarizer wrote: Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Mar 26 17:00:00 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036240.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Mar 26 17:00:06 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036241.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Mar 26 17:19:06 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036250.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Mar 26 17:46:54 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036265.html These are all the same bootstrap failures as yesterday. Jan-Jaap, I don't think anybody but you can diagnose thses. Subject: FAILED : Zope Buildbot / zopetoolkit-1.1-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Sat Mar 26 22:49:32 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036309.html This one is a timeout (looks like it was Ctrl-C'ed). - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Pc5cACgkQ+gerLs4ltQ66QQCgjMx/DO01UX+Qn88kSpI5x1ng DV4AmgK0yjeLVk6ehfGDkQVlANbDItep =On2g -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] CMF Tests: 4 OK, 2 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/27/2011 06:57 AM, CMF Tests Summarizer wrote: Subject: FAILED (failures=1) : CMF-trunk Zope-2.13 Python-2.6.5 : Linux From: CMF Tests Date: Sun Mar 27 01:38:28 EDT 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014600.html Subject: FAILED (failures=1) : CMF-trunk Zope-trunk Python-2.6.5 : Linux From: CMF Tests Date: Sun Mar 27 01:40:28 EDT 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014601.html These are both failures in the same formlib test: Failure in test /home/stefan/autotest/temp/python26-zope213-cmf23/src/Products.CMFDefault/Products/CMFDefault/formlib/schema.txt Failed doctest test for schema.txt File /home/stefan/autotest/temp/python26-zope213-cmf23/src/Products.CMFDefault/Products/CMFDefault/formlib/schema.txt, line 0 - -- File /home/stefan/autotest/temp/python26-zope213-cmf23/src/Products.CMFDefault/Products/CMFDefault/formlib/schema.txt, line 117, in schema.txt Failed example: content.foo_datetime == foo_zope_datetime Expected: True Got: False Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2Pcl4ACgkQ+gerLs4ltQ751wCghY1Q8wlXZlXm28AZU2eijCX4 iNEAn0Yo/lOniedyeTSC/V3gYY5wWGYV =wCSW -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope Tests: 86 OK, 14 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zope2.12-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Mar 25 16:08:23 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036147.html Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Mar 25 16:08:28 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036148.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Mar 25 16:27:30 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036158.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Fri Mar 25 16:57:25 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036172.html These are all failures in the bootstrap set, looking something like:: Traceback (most recent call last): File bootstrap.py, line 102, in module ws.find(pkg_resources.Requirement.parse(requirement)).location AttributeError: 'NoneType' object has no attribute 'location' program finished with exit code 1 Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2OGpoACgkQ+gerLs4ltQ5v3QCfVP2b8hAvPzwXkI20ZRCD1nYt qxUAnj6iYuwvsEMjb+XiU2sqZ11SRdkk =wSSS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] SVN: Zope/trunk/ Adding support for ``IStreamIterator`` to WSGI publishing machinery.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/26/2011 12:53 PM, Malthe Borch wrote:
Log message for revision 121131:
Adding support for ``IStreamIterator`` to WSGI publishing machinery.
Changed:
U Zope/trunk/doc/CHANGES.rst
U Zope/trunk/src/ZPublisher/WSGIPublisher.py
U Zope/trunk/src/ZPublisher/tests/test_WSGIPublisher.py
-=-
Modified: Zope/trunk/doc/CHANGES.rst
===
--- Zope/trunk/doc/CHANGES.rst2011-03-25 17:39:14 UTC (rev 121130)
+++ Zope/trunk/doc/CHANGES.rst2011-03-26 16:53:52 UTC (rev 121131)
@@ -11,6 +11,10 @@
Bugs Fixed
++
+- Fix `WSGIResponse` and `publish_module` functions such that they
+ support the `IStreamIterator` interface in addition to `file` (as
+ supported by `ZServer.HTTPResponse`).
+
- Made sure getConfiguration().default_zpublisher_encoding is set correctly.
- LP #713253: Prevent publication of acquired attributes, where the acquired
Modified: Zope/trunk/src/ZPublisher/WSGIPublisher.py
===
--- Zope/trunk/src/ZPublisher/WSGIPublisher.py2011-03-25 17:39:14 UTC
(rev 121130)
+++ Zope/trunk/src/ZPublisher/WSGIPublisher.py2011-03-26 16:53:52 UTC
(rev 121131)
@@ -30,6 +30,7 @@
from ZPublisher.Publish import dont_publish_class
from ZPublisher.Publish import get_module_info
from ZPublisher.Publish import missing_name
+from ZPublisher.Iterators import IStreamIterator
_NOW = None # overwrite for testing
def _now():
@@ -125,7 +126,7 @@
self.stdout.write(data)
def setBody(self, body, title='', is_error=0):
-if isinstance(body, file):
+if isinstance(body, file) or IStreamIterator.providedBy(body):
body.seek(0, 2)
length = body.tell()
body.seek(0)
This part of the patch can't possibly work in the general case: nothing
in IStreamIterator promises that 'seek' and 'tell' are available.
@@ -226,8 +227,10 @@
status, headers = response.finalize()
start_response(status, headers)
-if isinstance(response.body, file):
-result = response.body
+body = response.body
+
+if isinstance(body, file) or IStreamIterator.providedBy(body):
+result = body
else:
# If somebody used response.write, that data will be in the
# stdout StringIO, so we put that before the body.
Modified: Zope/trunk/src/ZPublisher/tests/test_WSGIPublisher.py
===
--- Zope/trunk/src/ZPublisher/tests/test_WSGIPublisher.py 2011-03-25
17:39:14 UTC (rev 121130)
+++ Zope/trunk/src/ZPublisher/tests/test_WSGIPublisher.py 2011-03-26
16:53:52 UTC (rev 121131)
@@ -370,6 +370,32 @@
app_iter = self._callFUT(environ, start_response, _publish)
self.assertTrue(app_iter is body)
+def test_response_is_stream(self):
+from ZPublisher.Iterators import IStreamIterator
+from zope.interface import implements
+
+class test_streamiterator:
+implements(IStreamIterator)
+data = hello
+done = 0
+
+def next(self):
+if not self.done:
+self.done = 1
+return self.data
+raise StopIteration
+
+_response = DummyResponse()
+_response._status = '200 OK'
+_response._headers = [('Content-Length', '4')]
+body = _response.body = test_streamiterator()
+environ = self._makeEnviron()
+start_response = DummyCallable()
+_publish = DummyCallable()
+_publish._result = _response
+app_iter = self._callFUT(environ, start_response, _publish)
+self.assertTrue(app_iter is body)
+
This test doesn't exercise the length checking branch (it would raise
AttributeError otherwise).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2OHwkACgkQ+gerLs4ltQ4O7wCgyazebfa92fAERR7fYs8jaR8w
Q3kAn2eZg5aqdeHAa8hMMppPTmCURYNF
=gieo
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/branches/2.13/buildout.cfg Restrict download sites to those which don't break the build.
Log message for revision 121122: Restrict download sites to those which don't break the build. Changed: U Zope/branches/2.13/buildout.cfg -=- Modified: Zope/branches/2.13/buildout.cfg === --- Zope/branches/2.13/buildout.cfg 2011-03-25 03:24:22 UTC (rev 121121) +++ Zope/branches/2.13/buildout.cfg 2011-03-25 14:59:44 UTC (rev 121122) @@ -1,6 +1,9 @@ [buildout] extensions = mr.developer +allow-hosts = +pypi.python.org +*.zope.org allow-picked-versions = false always-accept-server-certificate = true develop = . ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/buildout.cfg Restrict download sites to those which don't break the build.
Log message for revision 121123: Restrict download sites to those which don't break the build. Changed: U Zope/trunk/buildout.cfg -=- Modified: Zope/trunk/buildout.cfg === --- Zope/trunk/buildout.cfg 2011-03-25 14:59:44 UTC (rev 121122) +++ Zope/trunk/buildout.cfg 2011-03-25 15:23:58 UTC (rev 121123) @@ -1,6 +1,9 @@ [buildout] extensions = mr.developer +allow-hosts = +pypi.python.org +*.zope.org allow-picked-versions = false always-accept-server-certificate = true develop = . ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] zope.component test isolation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/25/2011 09:58 AM, Martin Aspeli wrote: I would suggest a good starting point would be to see if you can make plone.testing.zca clean. It should be pretty obvious what is currently a hack. If you got there, you effectively have stacking of component registries. plone.testing would be simpler, and zope.component.testing would be able to provide a simple way to stack configuration by layer without a plone.testing dependency. If you ignore the delete use case (which I think is a non-use case), I think this is quite achievable in a sprint, say. +1 to this approach. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2MpBsACgkQ+gerLs4ltQ7QQACgycVfipd/FvF6J8swGRJpZ2M9 SzcAniu9uvBS58WDcgxTxxllY+q8UmNX =Ljpu -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-CMF] RFC: Removing svn:externals from buildouts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I went to investigate fixing the SourceForge / setuptools build failures this monring and again bumped up against the use of svn:externals in the buildouts. My preferred mode for dealing with the Zope SVN server is via bzr-svn, but the svn:externals defeat that pattern. Since we are now using mr.developer anyway to pull in other dependencies, could we go ahead and switch to using it for all the checkouts? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2MojEACgkQ+gerLs4ltQ52sQCeItXRFjctolqh7ty9y2SXjvAX nDQAn3n/qB7zjwyui95M1Fgf52jVaaxJ =5svZ -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope Tests: 73 OK, 12 Failed, 4 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/24/2011 07:57 AM, Zope Tests Summarizer wrote: Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 23 16:02:31 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036010.html A bootstrap error (presumably tranisent network issue?): couldn't install setuptools. Jan-Jaap says he has fixed the issue. Subject: FAILED : Zope Buildbot / zopetoolkit-1.1-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 23 16:30:56 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036018.html Ditto. Subject: FAILED : Zope Buildbot / zopetoolkit-py2.6 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Wed Mar 23 16:36:40 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036021.html Ditto. Subject: FAILED : winbot / zc_buildout_dev py_254_win32 From: buildbot at winbot.zope.org Date: Wed Mar 23 17:27:21 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036035.html Subject: FAILED : winbot / zc_buildout_dev py_265_win32 From: buildbot at winbot.zope.org Date: Wed Mar 23 17:27:51 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036036.html Subject: FAILED : winbot / zc_buildout_dev py_265_win64 From: buildbot at winbot.zope.org Date: Wed Mar 23 17:28:02 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036037.html Subject: FAILED : winbot / zc_buildout_dev py_270_win32 From: buildbot at winbot.zope.org Date: Wed Mar 23 17:28:27 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036038.html Subject: FAILED : winbot / zc_buildout_dev py_270_win64 From: buildbot at winbot.zope.org Date: Wed Mar 23 17:28:39 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036039.html Jim said on Tuesday that he was investigating the buildout test breakage on Windows. Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Wed Mar 23 22:26:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036056.html IS there a 3.4 KGS doctor in the house? Subject: FAILED : winbot / z3c.rml_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 23 22:40:00 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036057.html This package looks to be mostly Stephan Richter's work, with contributions from some of the Usual Suspects. Subject: FAILED : winbot / z3c.coverage_py_265_32 From: buildbot at winbot.zope.org Date: Wed Mar 23 23:31:40 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036062.html This package looks to belong to Stephan, Adam Groszer, and Marius Gedminas. Subject: FAILED : winbot / z3c.recipe.paster_py_265_32 From: buildbot at winbot.zope.org Date: Thu Mar 24 00:02:42 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036064.html Thanks, Michael, for tackling this one! Subject: UNKNOWN : Zope-2.13 Python-2.6.5 : Linux From: Zope Tests Date: Thu Mar 24 02:08:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036071.html Subject: UNKNOWN : Zope-2.13-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Mar 24 02:10:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036072.html Subject: UNKNOWN : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Thu Mar 24 02:12:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036073.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Thu Mar 24 02:14:58 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/036074.html These are all failures to download the 'mechanize' package, due to the SourceForge bug (multiple 'Content-Type' headers). We can address via: - - Using setuptools-0.6c12dev-r88793.tar.gz (PJE has merged my workaround). - - Waiting for the SF guys to fix the bug, http://sourceforge.net/apps/trac/sourceforge/ticket/18486 - - Blocking the buildouts from using SF, as suggested yesterday by adding 'allow-hosts' to the buildout.cfg, as suggested by Laurence Rowe:: allow-hosts = *.python.org - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2LTOkACgkQ+gerLs4ltQ5iSgCdFfSkv3jkHxsQHMG6DfvLQwc/ /4MAoK8hLnivXa4nYsaExkrnUmeflu50 =U6PD -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https
Re: [Zope-dev] We need to get the board green
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/23/2011 02:40 AM, Wolfgang Schnerring wrote: * Tres Seaver tsea...@palladion.com [2011-03-22 14:18]: On 03/22/2011 03:59 AM, Adam GROSZER wrote: And please please kick the guilty one's a**, not the buildbot maintainer's. It does not make much sense to disable tests just because they fail. Leaving the packages as permanently failing is obviously not doing anything to motivate those maintainers. Leaving the board red is *de-motivating* to the community at large, who have to wade through failure reports for (apparently) unmaintained packages daily while trying to diagnose stuff which might have been broken by changes made the day before. I have to admit, I'm ignoring the buildbots completely at this time, (even though I think that having them in place could be very valuable), since all I perceive from them is failure-noise, and no trend of it getting less, at all, over the last few months. (That's my gut feeling, not based on research. It still makes me very much want to ignore them.) So, I agree with Tres: this situation is quite demotivating. But I also agree with Adam: I think the value of the buildbots is that they run tests, so disabling tests because they fail feels a little like closing our eyes shut because we don't want to see we're going to be falling off a cliff. I don't have much of an idea how to proceed, except maybe explicitly reducing the scope of the buildbots to a set of packages people around here care enough about that they want and will keep them green. Yup. That is why I was asking to suspend the 'z3c.*' packages which are failing: they haven't passed in months, and nobody seems motivated to fix them. Although they are in ragged shape at the moment, I *do* work to diagnose / fix failures in the ZTK and Zope2 tests. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2KBpMACgkQ+gerLs4ltQ4KfQCgka3lt0/wHdpb/lAIG0KJYp4b b7wAoIivluUBo5XFmF/oFIxUfM8nBqNF =G5fZ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 109 OK, 24 Failed, 4 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/23/2011 10:18 AM, Benji York wrote: On Wed, Mar 23, 2011 at 10:08 AM, Michael Howitz m...@gocept.com wrote: Am 23.03.2011 um 12:57 schrieb Zope Tests Summarizer: Test failures - [...] Subject: FAILED : Zope 3.4 Known Good Set / py2.4-32bit-linux From: buildbot at pov.lt Date: Tue Mar 22 22:26:52 EDT 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/035953.html While: Installing test. Getting distribution for 'ClientForm==0.2.9'. An internal error occured due to a bug in either zc.buildout or in a recipe being used: Traceback (most recent call last): ... File /var/lib/buildbot/slaves/zope-kgs/py2.4-32bit-linux/build/test/eggs/setuptools-0.6c11-py2.4.egg/setuptools/package_index.py, line 553, in _download_to size = int(headers[Content-Length]) ValueError: invalid literal for int(): 102936, 102936 Buildout tries to download ClientForm from sourceforge.net and seems to get a broken content-length header. I see the same problem when using distutils 0.6.14 since the last 3 or 4 days. But when I use wget the header seems to be correct or wget is smart enough to fix it. Both pip install and wget work here. Here are the headers wget retrieves: % wget -S http://wwwsearch.sourceforge.net/old/ClientForm/src/ClientForm-0.2.9.tar.gz --2011-03-23 10:17:20-- http://wwwsearch.sourceforge.net/old/ClientForm/src/ClientForm-0.2.9.tar.gz Resolving wwwsearch.sourceforge.net... 216.34.181.96 Connecting to wwwsearch.sourceforge.net|216.34.181.96|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Server: Apache/2.2.3 (CentOS) Last-Modified: Sat, 19 Jul 2008 13:29:12 GMT ETag: 19218-4526075b55a00 Content-Length: 102936 Expires: Fri, 25 Mar 2011 14:17:12 GMT Content-Type: application/x-gzip Content-Length: 102936 Date: Wed, 23 Mar 2011 14:17:12 GMT X-Varnish: 74437985 Age: 0 Via: 1.1 varnish Connection: keep-alive Length: 102936 (101K) [application/x-gzip] Saving to: `ClientForm-0.2.9.tar.gz' Multiple 'Content-Length' headers is definitely a Bad Thing. I filed a bug, which Mark Ramm has promised to escalate: https://sourceforge.net/apps/trac/sourceforge/ticket/18486 I have a patch for setuptools which works around it: http://bugs.python.org/setuptools/issue123 I'm not sure how to work around the issue at the moment. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2KBy4ACgkQ+gerLs4ltQ6WyQCfbKkGAvfbz9+AfhaKGgChGBq0 X98AoJ8CeMyptEUQ48npd85GvmVGEow/ =hzWS -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 109 OK, 24 Failed, 4 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/23/2011 10:49 AM, Laurence Rowe wrote: On 23 March 2011 14:43, Tres Seaver tsea...@palladion.com wrote: Multiple 'Content-Length' headers is definitely a Bad Thing. I filed a bug, which Mark Ramm has promised to escalate: https://sourceforge.net/apps/trac/sourceforge/ticket/18486 I have a patch for setuptools which works around it: http://bugs.python.org/setuptools/issue123 I'm not sure how to work around the issue at the moment. I always add the following to my buildout.cfg to avoid problems with random third party servers: allow-hosts = *.python.org *.plone.org launchpad.net (launchpad.net is there only for mocker which does not have a pypi release). Great point -- thanks for reminding me about 'allow-hosts'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2KCUUACgkQ+gerLs4ltQ4COwCgtnuYcMfxvw1EzkB1aYfq8YHa LB8An1M3Bw5fqXU/IORSz1ShWkE/swH9 =w7Hn -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] SVN: Products.GenericSetup/trunk/Products/GenericSetup/utils.py If exported value is None, attribute value is empty string (fixes a crash on contentrules configuration export)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 11:33 AM, Thomas Desvenain wrote:
Log message for revision 121096:
If exported value is None, attribute value is empty string (fixes a crash
on contentrules configuration export)
Changed:
U Products.GenericSetup/trunk/Products/GenericSetup/utils.py
-=-
Modified: Products.GenericSetup/trunk/Products/GenericSetup/utils.py
===
--- Products.GenericSetup/trunk/Products/GenericSetup/utils.py
2011-03-23 15:23:20 UTC (rev 121095)
+++ Products.GenericSetup/trunk/Products/GenericSetup/utils.py
2011-03-23 15:33:52 UTC (rev 121096)
@@ -350,7 +350,12 @@
for a_name in a_names:
wrapper.write()
-a_value = escape(attrs[a_name].value.encode('utf-8'), quote=True)
+a_value = attrs[a_name].value
+if a_value is None:
+a_value =
+else:
+a_value = escape(a_value.encode('utf-8'), quote=True))
+
wrapper.queue(' %s=%s' % (a_name, a_value))
if self.childNodes:
We also need a test which exercises / asserts this new behavior.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2KHi0ACgkQ+gerLs4ltQ7+UQCeMTuMFI2Eo2gSjxBbxNa23Hd0
ozYAnRle5ZDskFtBnZkeHYrvel0vUAUu
=SkWe
-END PGP SIGNATURE-
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: Products.GenericSetup/trunk/Products/GenericSetup/utils.py If exported value is None, attribute value is empty string (fixes a crash on contentrules configuration export)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 12:26 PM, Laurence Rowe wrote:
On 23 March 2011 16:22, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/23/2011 11:33 AM, Thomas Desvenain wrote:
Log message for revision 121096:
If exported value is None, attribute value is empty string (fixes a crash
on contentrules configuration export)
Changed:
U Products.GenericSetup/trunk/Products/GenericSetup/utils.py
-=-
Modified: Products.GenericSetup/trunk/Products/GenericSetup/utils.py
===
--- Products.GenericSetup/trunk/Products/GenericSetup/utils.py
2011-03-23 15:23:20 UTC (rev 121095)
+++ Products.GenericSetup/trunk/Products/GenericSetup/utils.py
2011-03-23 15:33:52 UTC (rev 121096)
@@ -350,7 +350,12 @@
for a_name in a_names:
wrapper.write()
-a_value = escape(attrs[a_name].value.encode('utf-8'),
quote=True)
+a_value = attrs[a_name].value
+if a_value is None:
+a_value =
+else:
+a_value = escape(a_value.encode('utf-8'), quote=True))
+
wrapper.queue(' %s=%s' % (a_name, a_value))
if self.childNodes:
We also need a test which exercises / asserts this new behavior.
In general in Zope, or at least with ZPT, None implies that an
attribute should be dropped. Would it be possible to preserve that
convention here?
That convention is not really as useful for XML data: it tends to break
stuff on import:
https://bugs.launchpad.net/zope-cmf/+bug/707927
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk2KJdcACgkQ+gerLs4ltQ6XFwCeOaZXSBKxb3OsqS1KH1SX0HJg
oT0AoJfxXOa/kjqvqGWcODIFkoir4RJY
=xaS8
-END PGP SIGNATURE-
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] We need to get the board green
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 03:59 AM, Adam GROSZER wrote: Hello, On Mon, 21 Mar 2011 11:56:05 -0400 you wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Too many never-resolve failures in our buildbots makes their output just noise: the amount of effort required to diagnose the cause of a failure seems to have no payoff if we don't get them each cleared up. I'm just about done with trying to diagnose them, myself, which is making me sad, as I *want* to be pleased with the quality of the software our community produces. I'd say revert back to the original procedure. The guilty dev has x days to fix the failure or the change gets reverted. PS: And please please kick the guilty one's a**, not the buildbot maintainer's. It does not make much sense to disable tests just because they fail. Chameleon is an external dependency, not managed as part of the Zope repository; I presume that the authors / maintainers of the z3c.* packages chose to depend on it with full knowledge of the risks that entails. If a new release of Chameleon breaks z3c.*, then it is the z3c.* maintainers whose tails need to be motivated: they should either get the exteranl dependency fixed, or work around it in their own packages (e.g., by pinning their dependency to a known good version, or by updating to use the newer APIs). Leaving the packages as permanently failing is obviously not doing anything to motivate those maintainers. Leaving the board red is *de-motivating* to the community at large, who have to wade through failure reports for (apparently) unmaintained packages daily while trying to diagnose stuff which might have been broken by changes made the day before. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2IobQACgkQ+gerLs4ltQ7ZeQCgopO4FTJE9KhgDsXy7OyCtw5V qbcAn3OG56JqlMqKAqOj/YjQRRf0VDoW =68up -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] CMF Tests: 3 OK, 3 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/22/2011 07:57 AM, CMF Tests Summarizer wrote: Summary of messages to the cmf-tests list. Period Mon Mar 21 12:00:00 2011 UTC to Tue Mar 22 12:00:00 2011 UTC. There were 6 messages: 6 from CMF Tests. Unknown --- Subject: UNKNOWN : CMF-2.2 Zope-2.13 Python-2.6.5 : Linux From: CMF Tests Date: Tue Mar 22 02:27:54 EDT 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014569.html Subject: UNKNOWN : CMF-trunk Zope-2.13 Python-2.6.5 : Linux From: CMF Tests Date: Tue Mar 22 02:29:54 EDT 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014570.html Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.6.5 : Linux From: CMF Tests Date: Tue Mar 22 02:31:54 EDT 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014571.html Weird. These are all failures trying to install 'machanize', with errors which look like:: File /usr/local/python2.6/lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/setuptools/package_index.py, line 553, in _download_to size = int(headers[Content-Length]) ValueError: invalid literal for int() with base 10: '382727, 382727' Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2ImUcACgkQ+gerLs4ltQ6+zwCg0ZTuCL2P74TBc+CbjUOYbwqm OckAniBItkMc1trdLmd0ckEhjO9mHQeS =D+5p -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-dev] We need to get the board green
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Too many never-resolve failures in our buildbots makes their output just noise: the amount of effort required to diagnose the cause of a failure seems to have no payoff if we don't get them each cleared up. I'm just about done with trying to diagnose them, myself, which is making me sad, as I *want* to be pleased with the quality of the software our community produces. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2HdRQACgkQ+gerLs4ltQ6zMQCgt2V6zhx/zKRJBmI3KSw5qD75 OgsAoJYLAmLGSMd9p+ZbrMqjZwDk99UU =l0kU -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Non-ZCML config for ZCA. (Was: Anyone want to do Google Summer of code mentoring for PSF?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/21/2011 02:13 PM, Jim Fulton wrote: On Mon, Mar 21, 2011 at 12:59 PM, Chris McDonough chr...@plope.com wrote: On Mon, 2011-03-21 at 15:53 +0100, Lennart Regebro wrote: ... It's easy and clear, but has the drawback of encouraging that registration is done on import time, while scanning separates the registration from the definition. I'm not sure how important that is. It's important to me, at least. Registration-on-import effectively requires that there only be a single component registry for all applications in a process. This is often fine for a given deployment, but as a framework strategy it seems very limiting. I'll note that this thread started with me saying: ZTK projects use ZCML too much. Ideally, ZCML should only have to be used when we want to override something. and: I think we ought to come up with a much cleaner way of defining default configuration. The intent of this thread, for me, was to come up with a cleaner way to define *default* configurations. The scope is narrower than all configuration. I'm thinking of use cases like the ones Tres mentioned where you now use default arguments to queryUtility and queryAdapter. Having a static way to express default configuration in no way prevents you from utilizing local registries, any more than hard coding defaults in calls to component-lookup APIs does. So where do static definitions make sense? I think static definitons make sense in library code when you own one of the interfaces, as in Tres' examples. I'm not positive, but I strongly suspect that this situation covers lots of registrations we now do in ZCML. I would argue that static definitions make sense in application code when you're pretty sure how you want to hook things up, although in this case, whether to express these application defaults in Python or ZCML (or whatever) is a matter of taste. (There are also some potential conflict issues that might make doing this sort of configuration statically unattractive.) One could argue about how much can be expressed as a static default configuration. Maybe elimination of all ZCML is too ambitious a goal, but I think we can avoid a lot of ZCML we have now. I'll probably make some concrete proposal at a later time. I trying to avoid saying more in this thread now, but I thought it was important try to be clearer aout what this thread was supposed to be about. FWIW, I just added 'queryAdapterFactory' and 'queryMultiAdapterFactory' APIs to zope.component on a branch: http://svn.zope.org/zope.component/branches/tseaver-queryAdapterFactory/ These APIs make the almost never overridden / dependency injection case as compact for adapters as for utilities. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2HqCYACgkQ+gerLs4ltQ7PFQCgnyoPFi8u8joVkA6wwDEL1ff0 IAcAn1l0s48CLGzVDRsF8tW32If7HCRm =WoQO -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Anyone want to do Google Summer of code mentoring for PSF?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2011 09:46 AM, Jim Fulton wrote: Problem === ZTK projects use ZCML too much. Ideally, ZCML should only have to be used when we want to override something. Solution sketch === I think we ought to come up with a much cleaner way of defining default configuration. (Pyramid does this by passing default values in adapter calls, but I think we can do a lot better than that.) I'm not confident that better is achievable for the classic dependency injection case (i.e., the default is the one you almost always want, except for unit testing). Typically, I define a utility interface *and* the default implementation in the module which mostly uses it. E.g.:: from zope.interface import Interface from zope.component import queryUtility class ISomePlugPoint(Interface): def __call__(foo, bar): blah blah # Look, Ma! No decorator! def defaultImpl(foo, bar): # DTRT for the normal case def clientFunction(request): impl = queryUtility(ISomePlugPoint, default=defaultImpl) Note the absence extra declarations for 'defaultImpl', and of extra syntax of any kind. In order to maintain good test isolation, I usually avoid memoizing the lookup (e.g. as a module scope variable). unless profiling shows that the lookup ends up on a critical path. This pattern even works outside of testing: if you do the frameworky thing and document how to override the utility as a policy, it becomes a trivial integration point. For adapters, the example is a bit noisier, because the component registry wants to call the factory for you:: from zope.interface import Interface from zope.component import queryAdapter class IAdaptsTo(Interface): def someMethod(): blah, blah. class DefaultImpl(object): # Note that we require no decorator or advice def __init__(self, context): self.context = context def someMethod(self): return 'whatever' def anotherClient(context, request): adapted = queryAdapter(context, IAdaptsTo) if adapted is None: adapted = DefaultImpl(context) # now use it (Note that memoization isn't a practical optimization doesn't work for adapters.) If we added a 'default_factory' argument to 'queryAdapter', we wouldn't need the 'if' statement, which would make this example as compact as the utility version. Or we could add a 'queryAdapterFactory' API instead, and have 'queryAdapter' use it (what is one more function call between friends? ;) The one downside I can see is giving up on the sugar^Wexpressivity of calling the interface directly -- I guess we could propagate the 'default_factory' argument through to the '__call__' of interface. Note that I *wanted* some extra sugar at one point (doing utility lookup when no arguments were passed to Interface.__call__), but I haven't missed that convenience much since I went on a low sugar diet with BFG / pyramid. I'd like to see us come up with a pythonic way to wire components up that can be overridden through registration (through zcml or otherwise). Ideally, the mechanism shouldn't feel like configuration but like programming. My example feels like programming to me: no ZCML, no decorators, and no advice needed up until the point you want to override the normal defaults. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2GND0ACgkQ+gerLs4ltQ6ynwCeJ1u/Bk3u8LGxhgR1jk2CFQP3 ZrcAoIuZbFCh2dpB611jKvOlUx48alqo =lvhO -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] Management of HEAD requests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/15/2011 08:39 AM, Jesus Cea wrote:
Using Zope 2.10 here.
When making a HEAD request, I get the last-modified time of the
script, and an application/octet-stream content type. The content
length is the script length.
When doing a GET request, I get a last-modified time of now and a
text/html content type. And the length is correct here.
As far as I know, the HEAD doesn't reach the script, it is processed
inside Zope. I would rather prefer to actually process the script but
give back only the headers.
That is, my problem is that HEAD and GET of the same object provide
completely different information about different objects (HEAD gives
info about the actual script, GET gives info of the script output). This
could be even a privacy issue, giving out script details people don't
need to know.
Is there any way to override this?. Suggestion?
I have issues, for instance, managing RSS feeds, since some clients do a
HEAD request instead of a conditional GET, for detecting new entries.
Thanks in advance, folks.
The default HED implementation is in 'webdav.Resource': it makes some
assumptions which are not appropriate. You can override it for your own
content objects: here is what App.ImageFile does::
security.declarePublic('HEAD')
def HEAD(self, REQUEST, RESPONSE):
RESPONSE.setHeader('Content-Type', self.content_type)
RESPONSE.setHeader('Last-Modified', self.lmh)
return ''
IMNSHO, there is absolutely no general way for a dynamic application to
satisfy clients that use HEAD instead of conditional get: the semantics
they rely on are meaningless for dynamically generated content.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1/hF8ACgkQ+gerLs4ltQ6BFACghX5SqjeN+NjEx5diEy5uokI1
zqAAnihau7b4qPt8ECNIErAtkz2sKWuN
=epmV
-END PGP SIGNATURE-
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] Fwd: Re: plans for tonight
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: Re: plans for tonight Date: Sat, 12 Mar 2011 17:11:40 + From: Brad Allen bal...@zeomega.com Jeff Rush planning a P http://twitter.com/#!/search?q=%23pyconyCon open space What's wrong with Zope at 6:30pm today. He's looking for constructive criticism, ideas for progress. After that we're planning to go to dinner at around 7:30pm after that to a nearby Mediterranean restaurant. I'm planning to make reservations at the restaurant, so please let me know if you'll be attending. Feel free to forward to friends who you think might be interested in either/both events. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk172/kACgkQ+gerLs4ltQ6cZACgrHMv9IST5D50hAGdH1ZSYcLo qJcAoKPAP8smp2euZ9tvd8jmOegLZFAZ =hio6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 84 OK, 16 Failed, 2 Unknown
return self.do_open(httplib.HTTPConnection, req) File c:\Python27_32_clean\lib\urllib2.py, line 1148, in do_open raise URLError(err) urllib2.URLError: urlopen error [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond BLANKLINE X - % --- Subject: FAILED : winbot / ZODB_dev py_265_win64 From: buildbot at winbot.zope.org Date: Fri Mar 4 19:13:37 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033927.html Bootstrap step failure: - % --- Download error: BadStatusLine: -- Some packages may not be found! Couldn't find index page for 'zc.buildout' (maybe misspelled?) Download error: [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond -- Some packages may not be found! No local packages or download links found for zc.buildout - % --- Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Fri Mar 4 22:12:16 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033945.html I think this is the same no-ouptput failure in zope.app.server's tests I dug into Mondeay (a hang inside zope.app.server.tests.test_mkzopeinstance.InputCollectionTestCase.test_get_password_manager - % --- test-zopeapp-zope.app.server failed with: /home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/bin/test-zopeapp-zope.app.server:64: DeprecationWarning: zope.testing.testrunner is deprecated in favour of zope.testrunner. import zope.testing.testrunner /home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/src/zope.testing/src/zope/testing/testrunner/formatter.py:28: DeprecationWarning: zope.testing.exceptions is deprecated in favour of zope.testrunner.exceptions from zope.testing.exceptions import DocTestFailureException /home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/src/zope.app.server/src/zope/app/server/tests/test_server.py:21: DeprecationWarning: zope.testing.doctest is deprecated in favour of the Python standard library doctest module from zope.testing import doctest /home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/src/zope.app.server/src/zope/app/server/tests/test_zpasswd.py:25: DeprecationWarning: zope.app.server.zpasswd has moved to zope.password.zpasswd. Import of zope.app.server.zpasswd will become unsupported in zope.app.server 3.6.0 from zope.app.server import zpasswd Running zope.testing.testrunner.layer.UnitTests tests: Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds. Ran 60 tests with 1 failures and 0 errors in 1.226 seconds. Tearing down left over layers: Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds. - % --- Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Fri Mar 4 22:12:49 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033946.html The same make-my-eyes-bleed doctest failure inside zope.testing.testrunner's tests I looked at yesterday (in /home/ccomb/ztk1.0dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testing/src/zope/testing/testrunner/testrunner-layers-buff.txt). Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Fri Mar 4 22:13:04 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033947.html This is the zope.app.server mystery hang. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1yRLcACgkQ+gerLs4ltQ4JxwCeNQBN3M1PpplM2urD9iKhn9yX ujsAniAmKtfr1sbCywC4r3PJZgGoKqAq =RM1T -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 90 OK, 16 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Thu Mar 3 22:13:09 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033836.html Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Thu Mar 3 22:13:26 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033837.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Thu Mar 3 22:13:40 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-March/033838.html This is some infuruating doctest-based failure in /home/ccomb/ztk1.0dev-slave/Python2.6.5-Linux-64bit/build/src/zope.testing/src/zope/testing/testrunner/testrunner-layers-buff.txt I'm never gonna diagnose that one. In re the various 'z3c' failures: if we can't pin them to an earlier lxml version, can we at least disable them until we have the lxml binary available? The noise is counterproductive. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1xCfcACgkQ+gerLs4ltQ7sWwCfTBklPQ4pEX7S4FV0qQUD+qC8 ossAn3mLDIF4nMoKRNsfKFtgwFgUjI6g =qw+J -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] CMF Tests: 5 OK, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: UNKNOWN : CMF-trunk Zope-trunk Python-2.6.5 : Linux From: CMF Tests Date: Thu Mar 3 02:27:08 EST 2011 URL: http://mail.zope.org/pipermail/cmf-tests/2011-March/014457.html Looks like a transient network failure: PyPI was unreachable. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1v+V4ACgkQ+gerLs4ltQ5RZgCgiqdmcM+O7+Ftzj+C6RZuW1BL +icAn1SqJsBwrwpNfEc67hiI+kPC9Tov =+XGb -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope Tests: 71 OK, 16 Failed
of the effect we intend. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1r20YACgkQ+gerLs4ltQ4qpACgquvggBLZNx5Q1oyW6QSGfbY5 jVwAn0CC5jdabaEUKSi4g8YuWvjXM1Ck =mTTk -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] can't register adapters for classes with metaclasses
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/27/2011 06:24 AM, Chris Withers wrote: This is particularly problematic when using the common case of SQLAlchemy declaratively mapped model classes. The attached unit test when run will fail with: Error in test test_provideAdapter (test_sa.TestAdapter) Traceback (most recent call last): File /usr/local/lib/python2.6/unittest.py, line 279, in run testMethod() File test_sa.py, line 25, in test_provideAdapter provideAdapter(MyAdapter,Model) File zope.component-3.10.0-py2.6.egg/zope/component/globalregistry.py, line 72, in provideAdapter base.registerAdapter(factory, adapts, provides, name, event=False) File zope.component-3.10.0-py2.6.egg/zope/component/registry.py, line 182, in registerAdapter required = _getAdapterRequired(factory, required) File zope.component-3.10.0-py2.6.egg/zope/component/registry.py, line 414, in _getAdapterRequired for r in required: TypeError: 'DeclarativeMeta' object is not iterable Why is that and how should I register an adapter against such a class? UTSL: the 'required' argument passed to 'registerAdapter' is supposed to be a sequence of interfaces or classes, not a single interface or class. If a class, then it must be something which can be passed to 'implementedBy'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1qiD0ACgkQ+gerLs4ltQ57FgCgqFiGvQ9c3A8q8QYo1JmUR4UY 3PsAoLZxrDy9Q56hedSAD1v4saHtXVhf =2veh -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-CMF] String exceptions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/25/2011 05:53 AM, Godefroid Chapelle wrote: Python2.6 has deprecated string exceptions. However, I find about 15 string exceptions in CMF 2.2 I guess this is just something that was forgotten. Can we consider this as a critical issue for next release ? Critial is not the right urgency for fixing deprecation warnings: nothing breaks, there is no security hole, etc. That being saie: you've done the hard work (finding them): just go ahead and check the fix in. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1nt8kACgkQ+gerLs4ltQ60cwCg2jOKaHLLrK3Wgdyf8zGnrSwt 4nAAnRDREjktOos4M1V9OeKSy+5MAsuF =xLje -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] Ready for a GenericSetup release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'd like to cut a GS 1.6.3 release from the trunk soonish -- is there any work going on that I should wait for? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1mdKEACgkQ+gerLs4ltQ7WtgCfQ33sXwpEFbpHP4t132nnKgz1 YH4AoJhS9dfP+7agvoTZrj9fdmhfQpoA =tAgp -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope Tests: 78 OK, 21 Failed
For: ('protectName', class
'zope.password.password.SSHAPasswordManager', 'match')
File
c:\buildslave\ztk_dev_py_265_win64\build\src\zope.password\src\zope\password\configure.zcml,
line 64.4-66.4
class class=.password.SSHAPasswordManager
allow interface=.interfaces.IMatchingPasswordManager /
/class
File
c:\buildslave\ztk_dev_py_265_win64\build\src\zope.password\src\zope\password\configure.zcml,
line 68.4-70.4
class class=.password.SSHAPasswordManager
allow interface=.interfaces.IMatchingPasswordManager /
/class
- - % ---
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1ibBsACgkQ+gerLs4ltQ6T8gCgyrYNBNlApnU8GJDv2MCWB2f/
HDUAn3XUDUlJvZCYUs3L1/ohmGt3YO6t
=z7yN
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 04:47 PM, Tres Seaver wrote: zope.dublincore.tests.test_timeannotators less strict? I am not a pypi owner of zope.dublincore, so Tres, could you do the honors? I made a stab at fixing the regex. If the dev checkouts start passing, then we can do a release. I tagged a 3.8.2 release and pushed it to PyPI. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1fzSUACgkQ+gerLs4ltQ6kXACgpN57yImuKB0JOs8or9aKoR7Z 0GYAoJxAy792QR0vRNnSvhKbEgsQU5a9 =HU1i -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/18/2011 03:21 AM, Jan-Jaap Driessen wrote:
On 18 February 2011 00:55, Simon Elbaz elbazsim...@gmail.com wrote:
Hi,
I have tried this code on Python 2.7.1 (r271:86832, Nov 27 2010, 18:30:46)
[MSC v.1500 32 bit (Intel)] on win32. It seems that it is possible to have
no milliseconds returned by datetime.now.
while 1:
... datetime.now(pytz.utc)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 17, 984000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, tzinfo=UTC)
...
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 15000, tzinfo=UTC)
datetime.datetime(2011, 2, 17, 23, 48, 18, 125000, tzinfo=UTC)
Traceback (most recent call last):
File stdin, line 2, in module
File
C:\Python27\lib\site-packages\pytz-2011b-py2.7.egg\pytz\__init__.py, li
ne 186, in utcoffset
KeyboardInterrupt
Simon
On Thu, Feb 17, 2011 at 4:58 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:
Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:03:12 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html
Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:18:08 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html
Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:25:31 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html
These three failures are due to a quirk in how datetime.datetime repr
works: if the 'microseconds' field happens to be zero, it isn't
printed, e.g.:
Expected:
datetime.datetime(DATETIME, tzinfo=UTC)
Got:
datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)
The regex (in zope.dublincore.tests.test_timeannotators), expects the
microseconds value to be present:
datetime_re = (
'[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
[0-9]{1,2}, '
'[0-9]{1,6}')
I have no idea why that value is suddenly exactly zero for the THA box.
Tres.
Simon,
Thank you for looking into this. I am kind of happy that the error can
be reproduced on a different windows machine.
Tres,
It is indeed 'special' that this error occurs only now. The windows
builds for zope.dublincore trunk have not shown this error:
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_3%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_5%20slave-win
http://dev.thehealthagency.com/buildbot/builders/zope.dublincore_trunk%20slave-win
How to proceed? Make the regex in
zope.dublincore.tests.test_timeannotators less strict?
I am not a pypi owner of zope.dublincore, so Tres, could you do the honors?
I made a stab at fixing the regex. If the dev checkouts start
passing, then we can do a release.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1e6PsACgkQ+gerLs4ltQ4ovgCeKYvKv+DfKGtkBB4aTiaXbBe4
Ec0AoMDWuEXSZ9ZwzQJrQH5gMQtemC5n
=1xra
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] PAS, AuthEncoding and zope.password
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/18/2011 04:19 PM, Martijn Pieters wrote: I was looking into bcrypt[1] support for PAS I found z3c.bcrypt, which implements zope.password compontents (named utilities). PAS, however, uses Zope2's AccessControl.AuthEncoding module to handle password encryption / hashing schemes. Now, while AuthEncoding certainly supports extending the available schemes, it does need additional glue-code to be able to reuse zope.password components. Moreover, we now have two places to maintain the various hashing and encryption schemes. We should at the very least convert PAS to use zope.password instead of AccessControl.AuthEncoding. With that change it is then at least trivial to support bcrypt as well, you simply install the additional z3c.bcrypt egg and be done with it. But would it make sense to convert Zope2 itself as well? We could make the AuthEncodings module simply a proxy (with deprecation warnings if need be) for zope.password components. Any objections to reworking both AuthEncoding and PAS? - -1 to any deprecation warnings; +0 otherwise. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1e6TUACgkQ+gerLs4ltQ7M6ACgpYmHdAFTuTb8M+aoGQFuIzza waIAn2AHG4xx/0wAe2ZE2Q2izgXPFPrK =7sQ8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 72 OK, 15 Failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/17/2011 06:58 AM, Zope Tests Summarizer wrote:
Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.5 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:03:12 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032218.html
Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:18:08 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032223.html
Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win
From: jdriessen at thehealthagency.com
Date: Wed Feb 16 15:25:31 EST 2011
URL: http://mail.zope.org/pipermail/zope-tests/2011-February/032226.html
These three failures are due to a quirk in how datetime.datetime repr
works: if the 'microseconds' field happens to be zero, it isn't
printed, e.g.:
Expected:
datetime.datetime(DATETIME, tzinfo=UTC)
Got:
datetime.datetime(2011, 2, 16, 20, 0, 43, tzinfo=UTC)
The regex (in zope.dublincore.tests.test_timeannotators), expects the
microseconds value to be present:
datetime_re = (
'[0-9]{4}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, [0-9]{1,2}, \
[0-9]{1,2}, '
'[0-9]{1,6}')
I have no idea why that value is suddenly exactly zero for the THA box.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1dRasACgkQ+gerLs4ltQ4R6ACfTV1r4oXAPee23hIDnA5GEaqQ
pX8AoJLVWCq35GWNDCxxqeDmyfezzg9U
=Lnxh
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 64 OK, 23 Failed, 2 Unknown
found for zc.buildout==1.4.4 - --- % -- - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1b8y0ACgkQ+gerLs4ltQ5WnACgkunwChKtJte+pLl8gPu1UlhA fGYAn3teOd7DNAE/t2TTsce8+h2OYsxH =/gB9 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 64 OK, 23 Failed, 2 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2011 10:54 AM, Tres Seaver wrote: Hmmm, what is this 'zope.configure' thing? --- % -- Couldn't find index page for 'zope.configure' (maybe misspelled?) Getting distribution for 'zope.configure'. --- % -- Looks like this checkin did it: --- % -- $ svn log --limit=1 $ZSVN/zope.copypastemove/trunk r120347 | tlotze | 2011-02-15 10:55:24 -0500 (Tue, 15 Feb 2011) | 1 line include zcml dependencies in configure.zcml, require the necessary packages via a zcml extra, added tests for zcml $ svn dirr -c 120347 $ZSVN/zope.copypastemove/trunk/setup.py --- setup.py (revision 120346) +++ setup.py (revision 120347) @@ -17,7 +17,7 @@ # Zope Toolkit policies as described by this documentation. ## -version = '3.8.1dev' +version = '3.9.0dev' from setuptools import setup, find_packages @@ -48,7 +48,12 @@ 'zope.testing', 'zope.traversing', 'zope.dublincore = 3.8', -]), +], + zcml=[ +'zope.component[zcml]', +'zope.configure', +'zope.security[zcml]', +]), install_requires=['setuptools', 'zope.annotation', 'zope.component', --- % -- I have checked in a fix for this typo. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1b9Y4ACgkQ+gerLs4ltQ4EWgCfXoEaCxkEPsSE++mxPnBI18kS 7/4An114LztA0YkdM5k08cL2Cquy1a0X =pgqm -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 81 OK, 18 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/08/2011 06:58 AM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Mon Feb 7 12:00:00 2011 UTC to Tue Feb 8 12:00:00 2011 UTC. There were 99 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 31 from buildbot at winbot.zope.org, 11 from ccomb at free.fr, 45 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2.14-py2.6 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Mon Feb 7 14:05:10 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031281.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Feb 7 14:17:33 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031284.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Mon Feb 7 14:19:08 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031286.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.1_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Feb 7 15:16:43 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031296.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Mon Feb 7 15:32:35 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031300.html I can't get to the buildbot pages for any of these failures. Jan-Jaap, can you investigate? Subject: FAILED : winbot / ztk_10 py_244_win32 From: buildbot at winbot.zope.org Date: Mon Feb 7 16:02:49 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/031304.html I just dumped the expected and got values to files and diffed them (why doesn't doctest show diff output by default?). It looks as though the 'samplelayers.layer122' tests are being skipped for some reason:: - - % --- $ diff -u /tmp/expected.txt /tmp/got.txt --- /tmp/expected.txt 2011-02-08 11:31:44.814287122 -0500 +++ /tmp/got.txt 2011-02-08 11:32:02.390287290 -0500 @@ -46,15 +46,6 @@ Tear down samplelayers.Layer121 in N.NNN seconds. Tear down samplelayers.Layer12 in N.NNN seconds. Tear down samplelayers.Layer1 in N.NNN seconds. -Running samplelayers.Layer122 tests: - Running in a subprocess. - Set up samplelayers.Layer1 in N.NNN seconds. - Set up samplelayers.Layer12 in N.NNN seconds. - Set up samplelayers.Layer122 in N.NNN seconds. - Ran 34 tests with 0 failures and 0 errors in N.NNN seconds. - Tear down samplelayers.Layer122 in N.NNN seconds. - Tear down samplelayers.Layer12 in N.NNN seconds. - Tear down samplelayers.Layer1 in N.NNN seconds. Running zope.testing.testrunner.layer.UnitTests tests: Running in a subprocess. Set up zope.testing.testrunner.layer.UnitTests in N.NNN seconds. @@ -62,5 +53,5 @@ Tear down zope.testing.testrunner.layer.UnitTests in N.NNN seconds. Tearing down left over layers: Tear down samplelayers.Layer1 in N.NNN seconds. -Total: 405 tests, 0 failures, 0 errors in N.NNN seconds. +Total: 371 tests, 0 failures, 0 errors in N.NNN seconds. False - - % --- - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1RcPwACgkQ+gerLs4ltQ4DAwCdGbfjWUkrWP9grJvmvUu2Ia2s sfcAoJ+hS/JRvg17c6r6TbKMidi2DcLz =Ep+f -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-Checkins] SVN: Zope/branches/2.10/ Don't publish acquired attributes if acquired object has no docstring.
Log message for revision 120124:
Don't publish acquired attributes if acquired object has no docstring.
See https://bugs.launchpad.net/zope2/+bug/713253/
Changed:
U Zope/branches/2.10/doc/CHANGES.txt
U Zope/branches/2.10/inst/WinBuilders/mk/zope.mk
U Zope/branches/2.10/inst/versions.py
U Zope/branches/2.10/lib/python/ZPublisher/BaseRequest.py
U Zope/branches/2.10/lib/python/ZPublisher/tests/testBaseRequest.py
U Zope/branches/2.10/setup.py
-=-
Modified: Zope/branches/2.10/doc/CHANGES.txt
===
--- Zope/branches/2.10/doc/CHANGES.txt 2011-02-05 19:45:07 UTC (rev 120123)
+++ Zope/branches/2.10/doc/CHANGES.txt 2011-02-06 13:26:26 UTC (rev 120124)
@@ -4,6 +4,14 @@
Change information for previous versions of Zope can be found in the
file HISTORY.txt.
+ Zope 2.10.13 (2011/02/04)
+
+Bugs fixed
+
+ - Prevent publication of acquired attributes, where the acquired
+object does not have a docstring.
+https://bugs.launchpad.net/zope2/+bug/713253/
+
Zope 2.10.12 (2010/09/01)
Bugs fixed
Modified: Zope/branches/2.10/inst/WinBuilders/mk/zope.mk
===
--- Zope/branches/2.10/inst/WinBuilders/mk/zope.mk 2011-02-05 19:45:07 UTC
(rev 120123)
+++ Zope/branches/2.10/inst/WinBuilders/mk/zope.mk 2011-02-06 13:26:26 UTC
(rev 120124)
@@ -1,4 +1,4 @@
-ZOPEVERSION = 2.10.12-final
+ZOPEVERSION = 2.10.13-final
ZOPEDIRNAME := Zope-$(ZOPEVERSION)
ZOPE_REQUIRED_FILES=tmp/$(ZOPEDIRNAME).tgz
Modified: Zope/branches/2.10/inst/versions.py
===
--- Zope/branches/2.10/inst/versions.py 2011-02-05 19:45:07 UTC (rev 120123)
+++ Zope/branches/2.10/inst/versions.py 2011-02-06 13:26:26 UTC (rev 120124)
@@ -1,5 +1,5 @@
ZOPE_MAJOR_VERSION = '2.10'
-ZOPE_MINOR_VERSION = '12'
+ZOPE_MINOR_VERSION = '13'
ZOPE_BRANCH_NAME= '$Name$'[6:] or 'no-branch'
# always start prerelease branches with '0' to avoid upgrade
Modified: Zope/branches/2.10/lib/python/ZPublisher/BaseRequest.py
===
--- Zope/branches/2.10/lib/python/ZPublisher/BaseRequest.py 2011-02-05
19:45:07 UTC (rev 120123)
+++ Zope/branches/2.10/lib/python/ZPublisher/BaseRequest.py 2011-02-06
13:26:26 UTC (rev 120124)
@@ -116,23 +116,21 @@
# Again, clear any error status created by
__bobo_traverse__
# because we actually found something:
request.response.setStatus(200)
-return subobject
except AttributeError:
pass
# Lastly we try with key access:
-try:
-subobject = object[name]
-except TypeError: # unsubscriptable
-raise KeyError(name)
+if subobject is None:
+try:
+subobject = object[name]
+except TypeError: # unsubscriptable
+raise KeyError(name)
# Ensure that the object has a docstring, or that the parent
# object has a pseudo-docstring for the object. Objects that
# have an empty or missing docstring are not published.
doc = getattr(subobject, '__doc__', None)
-if doc is None:
-doc = getattr(object, '%s__doc__' % name, None)
if not doc:
raise Forbidden(
The object at %s has an empty or missing \
Modified: Zope/branches/2.10/lib/python/ZPublisher/tests/testBaseRequest.py
===
--- Zope/branches/2.10/lib/python/ZPublisher/tests/testBaseRequest.py
2011-02-05 19:45:07 UTC (rev 120123)
+++ Zope/branches/2.10/lib/python/ZPublisher/tests/testBaseRequest.py
2011-02-06 13:26:26 UTC (rev 120124)
@@ -166,6 +166,13 @@
r = self._makeOne(root)
self.assertRaises(NotFound, r.traverse, 'folder/objBasic/noview')
+def test_traverse_acquired_attribute_without_docstring(self):
+from ZPublisher import NotFound
+root, folder = self._makeRootAndFolder()
+root._setObject('objBasic', DummyObjectWithoutDocstring())
+r = self._makeOne(root)
+self.assertRaises(NotFound, r.traverse, 'folder/objBasic')
+
def test_traverse_class_without_docstring(self):
from ZPublisher import NotFound
root, folder = self._makeRootAndFolder()
Modified: Zope/branches/2.10/setup.py
===
--- Zope/branches/2.10/setup.py 2011-02-05 19:45:07 UTC (rev 120123)
+++ Zope/branches/2.10/setup.py 2011-02-06 13:26:26 UTC (rev 120124)
@@ -462,7 +462,7 @@
setup(name='Zope',
author=AUTHOR,
- version=2.10.7-dev,
+ version=2.10.13,
[Zope-Checkins] SVN: Zope/tags/2.10.13/ Tag 2.10.13 release.
Log message for revision 120125: Tag 2.10.13 release. Changed: A Zope/tags/2.10.13/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.11.8/ Tag 2.11.8 release.
Log message for revision 120127: Tag 2.11.8 release. Changed: A Zope/tags/2.11.8/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.12/ Don't publish acquired attributes if acquired object has no docstring.
Log message for revision 120128:
Don't publish acquired attributes if acquired object has no docstring.
See https://bugs.launchpad.net/zope2/+bug/713253/
Changed:
U Zope/branches/2.12/doc/CHANGES.rst
U Zope/branches/2.12/setup.py
U Zope/branches/2.12/src/ZPublisher/BaseRequest.py
U Zope/branches/2.12/src/ZPublisher/tests/testBaseRequest.py
-=-
Modified: Zope/branches/2.12/doc/CHANGES.rst
===
--- Zope/branches/2.12/doc/CHANGES.rst 2011-02-06 13:28:22 UTC (rev 120127)
+++ Zope/branches/2.12/doc/CHANGES.rst 2011-02-06 13:30:29 UTC (rev 120128)
@@ -5,12 +5,15 @@
Change information for previous versions of Zope can be found at
http://docs.zope.org/zope2/releases/.
-2.12.15 (unreleased)
+2.12.15 (2011-02-04)
Bugs Fixed
++
+- LP #713253: Prevent publication of acquired attributes, where the acquired
+ object does not have a docstring.
+
- Fix `LazyMap` to avoid unnecessary function calls.
2.12.14 (2010-12-07)
Modified: Zope/branches/2.12/setup.py
===
--- Zope/branches/2.12/setup.py 2011-02-06 13:28:22 UTC (rev 120127)
+++ Zope/branches/2.12/setup.py 2011-02-06 13:30:29 UTC (rev 120128)
@@ -16,7 +16,7 @@
from setuptools import setup, find_packages, Extension
setup(name='Zope2',
-version='2.12.15dev',
+version='2.12.15',
url='http://www.zope.org',
license='ZPL 2.1',
description='Zope2 application server / web framework',
Modified: Zope/branches/2.12/src/ZPublisher/BaseRequest.py
===
--- Zope/branches/2.12/src/ZPublisher/BaseRequest.py2011-02-06 13:28:22 UTC
(rev 120127)
+++ Zope/branches/2.12/src/ZPublisher/BaseRequest.py2011-02-06 13:30:29 UTC
(rev 120128)
@@ -120,23 +120,21 @@
# Again, clear any error status created by
__bobo_traverse__
# because we actually found something:
request.response.setStatus(200)
-return subobject
except AttributeError:
pass
# Lastly we try with key access:
-try:
-subobject = object[name]
-except TypeError: # unsubscriptable
-raise KeyError(name)
+if subobject is None:
+try:
+subobject = object[name]
+except TypeError: # unsubscriptable
+raise KeyError(name)
# Ensure that the object has a docstring, or that the parent
# object has a pseudo-docstring for the object. Objects that
# have an empty or missing docstring are not published.
doc = getattr(subobject, '__doc__', None)
-if doc is None:
-doc = getattr(object, '%s__doc__' % name, None)
if not doc:
raise Forbidden(
The object at %s has an empty or missing \
Modified: Zope/branches/2.12/src/ZPublisher/tests/testBaseRequest.py
===
--- Zope/branches/2.12/src/ZPublisher/tests/testBaseRequest.py 2011-02-06
13:28:22 UTC (rev 120127)
+++ Zope/branches/2.12/src/ZPublisher/tests/testBaseRequest.py 2011-02-06
13:30:29 UTC (rev 120128)
@@ -304,6 +304,14 @@
r = self._makeOne(root)
self.assertRaises(NotFound, r.traverse, 'folder/objBasic/noview')
+def test_traverse_acquired_attribute_without_docstring(self):
+from ZPublisher import NotFound
+root, folder = self._makeRootAndFolder()
+root._setObject('objBasic',
+self._makeObjectWithEmptyDocstring())
+r = self._makeOne(root)
+self.assertRaises(NotFound, r.traverse, 'folder/objBasic')
+
def test_traverse_class_without_docstring(self):
from ZPublisher import NotFound
root, folder = self._makeRootAndFolder()
___
Zope-Checkins maillist - Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.12.13/2.12/ Tag 2.12.13 release.
Log message for revision 120129: Tag 2.12.13 release. Changed: A Zope/tags/2.12.13/2.12/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.12.13/2.12/ Wrong location
Log message for revision 120130: Wrong location Changed: D Zope/tags/2.12.13/2.12/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.12.15/ Tag 2.12.15 release.
Log message for revision 120131: Tag 2.12.15 release. Changed: A Zope/tags/2.12.15/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/2.13/ Don't publish acquired attributes if acquired object has no docstring.
Log message for revision 120132:
Don't publish acquired attributes if acquired object has no docstring.
See https://bugs.launchpad.net/zope2/+bug/713253/
Changed:
U Zope/branches/2.13/doc/CHANGES.rst
U Zope/branches/2.13/setup.py
U Zope/branches/2.13/src/ZPublisher/BaseRequest.py
U Zope/branches/2.13/src/ZPublisher/tests/testBaseRequest.py
-=-
Modified: Zope/branches/2.13/doc/CHANGES.rst
===
--- Zope/branches/2.13/doc/CHANGES.rst 2011-02-06 13:38:53 UTC (rev 120131)
+++ Zope/branches/2.13/doc/CHANGES.rst 2011-02-06 13:42:22 UTC (rev 120132)
@@ -5,7 +5,7 @@
Change information for previous versions of Zope can be found at
http://docs.zope.org/zope2/releases/.
-2.13.3 (unreleased)
+2.13.3 (2011-02-04)
---
Features Added
@@ -17,6 +17,9 @@
Bugs Fixed
++
+
+- LP #713253: Prevent publication of acquired attributes, where the acquired
+ object does not have a docstring.
2.13.2 (2011-01-19)
Modified: Zope/branches/2.13/setup.py
===
--- Zope/branches/2.13/setup.py 2011-02-06 13:38:53 UTC (rev 120131)
+++ Zope/branches/2.13/setup.py 2011-02-06 13:42:22 UTC (rev 120132)
@@ -23,7 +23,7 @@
setup(name='Zope2',
-version='2.13.3dev',
+version='2.13.3',
url='http://zope2.zope.org',
license='ZPL 2.1',
description='Zope2 application server / web framework',
Modified: Zope/branches/2.13/src/ZPublisher/BaseRequest.py
===
--- Zope/branches/2.13/src/ZPublisher/BaseRequest.py2011-02-06 13:38:53 UTC
(rev 120131)
+++ Zope/branches/2.13/src/ZPublisher/BaseRequest.py2011-02-06 13:42:22 UTC
(rev 120132)
@@ -126,15 +126,15 @@
# Again, clear any error status created by
__bobo_traverse__
# because we actually found something:
request.response.setStatus(200)
-return subobject
except AttributeError:
pass
# Lastly we try with key access:
-try:
-subobject = object[name]
-except TypeError: # unsubscriptable
-raise KeyError(name)
+if subobject is None:
+try:
+subobject = object[name]
+except TypeError: # unsubscriptable
+raise KeyError(name)
# Ensure that the object has a docstring, or that the parent
# object has a pseudo-docstring for the object. Objects that
Modified: Zope/branches/2.13/src/ZPublisher/tests/testBaseRequest.py
===
--- Zope/branches/2.13/src/ZPublisher/tests/testBaseRequest.py 2011-02-06
13:38:53 UTC (rev 120131)
+++ Zope/branches/2.13/src/ZPublisher/tests/testBaseRequest.py 2011-02-06
13:42:22 UTC (rev 120132)
@@ -335,6 +335,14 @@
r = self._makeOne(root)
self.assertRaises(NotFound, r.traverse, 'folder/objBasic/noview')
+def test_traverse_acquired_attribute_without_docstring(self):
+from ZPublisher import NotFound
+root, folder = self._makeRootAndFolder()
+root._setObject('objBasic',
+self._makeObjectWithEmptyDocstring())
+r = self._makeOne(root)
+self.assertRaises(NotFound, r.traverse, 'folder/objBasic')
+
def test_traverse_class_without_docstring(self):
from ZPublisher import NotFound
root, folder = self._makeRootAndFolder()
___
Zope-Checkins maillist - Zope-Checkins@zope.org
https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/tags/2.13.3/ Tag 2.13.13 release.
Log message for revision 120133: Tag 2.13.13 release. Changed: A Zope/tags/2.13.3/ -=- ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-CMF] SVN: Products.CMFCore/trunk/Products/CMFCore/ Removed os.path.walk call in windows development mode
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2011 06:17 PM, Nikolay Kim wrote: well, we tested on modern windows, everything seem to work. but problem is, it is not possible to develop on windows without this patch. it just too slow. removing 'os.path.walk' makes development mode as fast as on linux On Wed, 2011-02-02 at 18:12 -0500, Tres Seaver wrote: On 02/02/2011 05:30 PM, Nikolay Kim wrote: Modified: Products.CMFCore/trunk/Products/CMFCore/DirectoryView.py === --- Products.CMFCore/trunk/Products/CMFCore/DirectoryView.py 2011-02-02 22:30:34 UTC (rev 120067) +++ Products.CMFCore/trunk/Products/CMFCore/DirectoryView.py 2011-02-02 22:30:48 UTC (rev 120068) @@ -106,7 +106,6 @@ class DirectoryInformation: data = None _v_last_read = 0 -_v_last_filelist = [] # Only used on Win32 def __init__(self, filepath, reg_key, ignore=ignore): self._filepath = filepath @@ -159,23 +158,13 @@ if not Globals.DevelopmentMode: return 0 mtime=0 -filelist=[] try: mtime = os.stat(self._filepath)[8] -if platform == 'win32': -# some Windows directories don't change mtime -# when a file is added to or deleted from them :-( -# So keep a list of files as well, and see if that -# changes -os.path.walk(self._filepath, self._walker, filelist) -filelist.sort() except: logger.exception(Error checking for directory modification) -if mtime != self._v_last_read or filelist != self._v_last_filelist: +if mtime != self._v_last_read: self._v_last_read = mtime -self._v_last_filelist = filelist - return 1 return 0 Nikolay, The code you removed was there to prevent very real problems some people experienced when running on Windows in development mode: are you sure that such users have all moved on to modern enough versions to make this change a better tradeoff? Maybe we should allow restoring the safe but slow behavior with an environment variable? (Sorry for the confusion about ths list -- my earlier message went to Nikolay directly, but to the zope-cmf list via gmane). Can anybody else comment who is doing CMF-based work on Windows? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1J7bgACgkQ+gerLs4ltQ6KXQCdGNoujM2AjD7dsmItPHvNNGKE x6gAoNIhP49Cz3ecIQiSEpizoPk0cHLy =skx6 -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope Tests: 89 OK, 8 Failed, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/01/2011 06:58 AM, Zope Tests Summarizer wrote: Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Mon Jan 31 21:28:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030632.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Mon Jan 31 21:28:59 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030633.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Mon Jan 31 21:29:06 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030634.html These are the same build failures (due to a missing pin of zope.testbrowser?): the buildout step fails to create the 'test-zopeapp' script, but exits with RC 0:: - --- % - Installing test-zopeapp. While: Installing test-zopeapp. Getting distribution for 'zope.testbrowser=3.11'. Error: Picked: zope.testbrowser = 3.11.1 program finished with exit code 0 - --- % - Subject: FAILED : winbot / zope.annotation_py_265_32 From: buildbot at winbot.zope.org Date: Mon Jan 31 23:15:47 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030642.html This one blew up during bootstrap:: - --- % - error: Download error for http://pypi.python.org/packages/source/z/zc.buildout/zc.buildout-1.5.2.tar.gz: [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond Traceback (most recent call last): File c:\buildmaster\bootstrap.py, line 112, in module ) == 0 AssertionError program finished with exit code 1 - --- % - Subject: UNKNOWN : Zope-2.13 Python-2.6.5 : Linux From: Zope Tests Date: Tue Feb 1 01:12:43 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-February/030669.html This one looks like a (transient) network failure:: - --- % - Download error: [Errno 104] Connection reset by peer -- Some packages may not be found! Couldn't find index page for 'zope.location' (maybe misspelled?) Download error: [Errno 101] Network is unreachable -- Some packages may not be found! Getting distribution for 'zope.location==3.9.0'. While: Installing test. Getting distribution for 'zope.location==3.9.0'. Error: Couldn't find a distribution for 'zope.location==3.9.0'. - --- % - Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1IOMcACgkQ+gerLs4ltQ47RwCglO9XYZ7VacR0vi4qFX13UMmY +gcAn2qIIABUE+xTXerrpCGnG1swipU/ =AHqu -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 68 OK, 8 Failed, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2011 06:58 AM, Zope Tests Summarizer wrote: Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 64bit From: ccomb at free.fr Date: Fri Jan 28 21:29:09 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030348.html Subject: FAILED : ZTK 1.0dev / Python2.6.5 Linux 64bit From: ccomb at free.fr Date: Fri Jan 28 21:29:14 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030349.html Subject: FAILED : ZTK 1.0dev / Python2.5.5 Linux 64bit From: ccomb at free.fr Date: Fri Jan 28 21:29:17 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030350.html These three are due to a version mismatch: the buildout doesnt create the 'test-zopeapp' script:: Installing test-zopeapp. While: Installing test-zopeapp. Getting distribution for 'zope.testbrowser=3.11'. Error: Picked: zope.testbrowser = 3.11.1 Subject: FAILED : Zope Buildbot / zopetoolkit-1.0-py2.4 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sat Jan 29 02:08:25 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030396.html I can't load the failed test output on this page. Subject: UNKNOWN : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Sat Jan 29 00:21:21 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/030376.html I'm not able to load the summary page at all. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1EHykACgkQ+gerLs4ltQ4kVQCfTDuilSHEoR4MOtMclYWdYOWl tf4An1yQnlooon8jigMazzyXvuV+ZqI4 =JACL -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Announcement: 2011 Zope Foundation Board Elections and General Meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (apologies in advance for the cross-post: we need this to reach the whole Zope community). The Zope Foundation board is pleased to announce that the regular 2011 general meeting of the foundation will be held on Wednesday, 16 March 2011, at 15:00 UTC. The meeting will be conducted via IRC at the following channel: irc://irc.freenode.net/#zope-foundation Prior to that meeting, the current board will conduct an elections in which foundation members will select seven (7) board members in accordance with the foundation bylaws[1]. Summary - --- - - Nominations open via the foundat...@zope.org mailing list until Friday, 2011-02-11. - - Voting via e-mail to a closed mailing list, from Wednesday, 2011-02-16 through Friday, 2011-03-04. - - Votes tallied by representatives of the current board, using Meek and Warrent STV method using OpenSTV software. - - General meeting and seating of the new board, Wednesday, 2011-03-16. Procedure for Elections - --- The procedure for the elections is as follows: - - Foundation members may nominate any member by responding to the board's announcement on the foundat...@zope.org mailing list. Nominations will remain open until Friday, 2011-02-11, 23:00 UTC. - - At the close of the nominations period, the board will create a new mailman list, 'zf-elections-2011', and approve all ZF members to post to the list.. In order to preserve anonymity of votes, foundation members will not be subscribers to the list; access to the list archives will be restricted to the tellers appointed by the board. - - On Wednesday, 2011-02-16, the Secretary will send an e-mail announcing the opening of the voting period. This e-mail will contain the ballot, with careful instructions about how to rank preferences in the reply. The Reply-to header of this e-mail will be set to the 'zf-elections-2011' list. - - ZF members will vote by replying to that e-mail. Voting will remain open until Friday, 2011-03-04, 23:00 UTC. - - At the close of voting, the board will appoint two of its members as tellers. The tellers will use the list archive to tabulate the members' votes, using the OpenSTV application[2] configured to use the Meek and Warren STV method[3]. The tellers will report the election results, along with the raw tallies, at a special board meeting to be held on Tuesday, 2011-03-15, 15:00 UTC. - - After canvassing the results from the tellers, the board will notify all nominees of the success / failure of their candidacy, thanking them for their willingness to serve. - - At the general meeting, the last item on the agenda will the announcement of the election results, including a vote to seat the board. An online version of this announcement is available at: http://foundation.zope.org/news/2011_election_and_general_meeting/ References - -- [1] http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf [2] http://stv.sourceforge.net/aboutopenstv [3] http://stv.sourceforge.net/votingmethods/meek Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1B8owACgkQ+gerLs4ltQ7OaACfSBCwcbLsELAk/n9eW0CblmMz UvcAn0a1hIhLiocRo8GG431ccPnzDK7/ =2p6F -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] MemoryError: out of memory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/26/2011 03:19 PM, Jonathan Salazar Santos wrote:
Hi Comunity,
I have been in troubles with Zope2.10.5-final since 4 moths ago,
related to the MemoryError: out of memory (in the event.log), every
three or fourth days (more or less) the Zope starts to say in our web:
value error: Memory, and stops to serve some pages (not all), usually
the pages that serve file contents (to download, convert to pdf or
view online). I solve the problem (when appears) by rebooting the zope
server, but its not a solutions, because I dont know when the error
its coming ¿Can you help me to giving me some light to solve the
problem? I have 2gb of RAM, and the server (FreeBSD) it says
no-overloaded, just have 2 services, web(zope) and database(mysql). I
think its something related to the cache memory or kind of (I changed
some values in config file but not success). See some of my event.log
Traceback (innermost last):
Module ZPublisher.Publish, line 119, in publish
Module ZPublisher.mapply, line 88, in mapply
Module ZPublisher.Publish, line 42, in call_object
Module OFS.DTMLMethod, line 144, in __call__
- DTMLMethod at //index_html used for
//suscribete/adminNewsletter
- URL: http:///index_html/manage_main
- Physical Path: //index_html
Module DocumentTemplate.DT_String, line 476, in __call__
Module OFS.DTMLMethod, line 137, in __call__
- DTMLMethod at //suscribete/adminNewsletter/third_header
- URL: http:///suscribete/adminNewsletter/third_header/manage_main
- Physical Path: //suscribete/adminNewsletter/third_header
Module DocumentTemplate.DT_String, line 476, in __call__
Module DocumentTemplate.DT_In, line 703, in renderwob
Module Products.MailHost.SendMailTag, line 114, in render
Module Products.MIMETools.MIMETag, line 198, in render
Module MimeWriter, line 177, in lastpart
MemoryError: out of memory
The aliases feature of the stock Shared.DC.ZRDB.Results.Results class
has a leak, due to an uncollectable cycle created between the alias
objects and the record class generated *for each query*. If your app
makes heavy use of stock ZSQL methods, you are probably going to have to
plan to monitor the server's RAM usage and reboot as it gets close to
the limit.
If you are confident either that your application does not need the
alias feature (your SQL queries all spell the column names using the
canonical spelling for your SQL server), or that you can modify them
to do so, you might try applying the attached patch, which removes the
aliase feature.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk1BmW4ACgkQ+gerLs4ltQ41VgCfeqvB4gRnQAd2xY+EHjkbTwiP
7xcAnA7GGngAry7jqXbCWDBq8ugafIw8
=cPGc
-END PGP SIGNATURE-
=== modified file 'lib/python/Shared/DC/ZRDB/Results.py'
--- lib/python/Shared/DC/ZRDB/Results.py 2005-11-18 14:39:19 +
+++ lib/python/Shared/DC/ZRDB/Results.py 2011-01-27 16:09:13 +
@@ -38,7 +38,6 @@
self._names=names=[]
self._schema=schema={}
self._data_dictionary=dd={}
-aliases=[]
if zbrains is None: zbrains=NoBrains
i=0
for item in items:
@@ -49,10 +48,6 @@
if schema.has_key(name):
raise ValueError, 'Duplicate column name, %s' % name
schema[name]=i
-n=name.lower()
-if n != name: aliases.append((n, SQLAlias(name)))
-n=name.upper()
-if n != name: aliases.append((n, SQLAlias(name)))
dd[name]=item
names.append(name)
i=i+1
@@ -70,11 +65,6 @@
if k[:2]=='__':
setattr(r,k,getattr(Record,k))
-# Add SQL Aliases
-for k, v in aliases:
-if not hasattr(r, k):
-setattr(r, k, v)
-
if hasattr(brains, '__init__'):
binit=brains.__init__
if hasattr(binit,'im_func'): binit=binit.im_func
___
Zope maillist - Zope@zope.org
https://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] MemoryError: out of memory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/27/2011 11:12 AM, Tres Seaver wrote: The aliases feature of the stock Shared.DC.ZRDB.Results.Results class has a leak, due to an uncollectable cycle created between the alias objects and the record class generated *for each query*. If your app makes heavy use of stock ZSQL methods, you are probably going to have to plan to monitor the server's RAM usage and reboot as it gets close to the limit. If you are confident either that your application does not need the alias feature (your SQL queries all spell the column names using the canonical spelling for your SQL server), or that you can modify them to do so, you might try applying the attached patch, which removes the aliase feature. I should note that I never use the stock results class (or SQL methods) any longer: instead, I use the 'sqladapters' product we wrote when we first discovered the leak: http://agendaless.com/Members/tseaver/software/sqladapters/sqladapters-1.0/ Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1BmyoACgkQ+gerLs4ltQ7JpQCgw76+ltS33nnUoDJQepGAWW2c hkMAoNn0PsLtLY1Fp91NxZjbvnv6kbCW =DWNc -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Announcement: 2011 Zope Foundation Board Elections and General Meeting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (apologies in advance for the cross-post: we need this to reach the whole Zope community). The Zope Foundation board is pleased to announce that the regular 2011 general meeting of the foundation will be held on Wednesday, 16 March 2011, at 15:00 UTC. The meeting will be conducted via IRC at the following channel: irc://irc.freenode.net/#zope-foundation Prior to that meeting, the current board will conduct an elections in which foundation members will select seven (7) board members in accordance with the foundation bylaws[1]. Summary - --- - - Nominations open via the foundat...@zope.org mailing list until Friday, 2011-02-11. - - Voting via e-mail to a closed mailing list, from Wednesday, 2011-02-16 through Friday, 2011-03-04. - - Votes tallied by representatives of the current board, using Meek and Warrent STV method using OpenSTV software. - - General meeting and seating of the new board, Wednesday, 2011-03-16. Procedure for Elections - --- The procedure for the elections is as follows: - - Foundation members may nominate any member by responding to the board's announcement on the foundat...@zope.org mailing list. Nominations will remain open until Friday, 2011-02-11, 23:00 UTC. - - At the close of the nominations period, the board will create a new mailman list, 'zf-elections-2011', and approve all ZF members to post to the list.. In order to preserve anonymity of votes, foundation members will not be subscribers to the list; access to the list archives will be restricted to the tellers appointed by the board. - - On Wednesday, 2011-02-16, the Secretary will send an e-mail announcing the opening of the voting period. This e-mail will contain the ballot, with careful instructions about how to rank preferences in the reply. The Reply-to header of this e-mail will be set to the 'zf-elections-2011' list. - - ZF members will vote by replying to that e-mail. Voting will remain open until Friday, 2011-03-04, 23:00 UTC. - - At the close of voting, the board will appoint two of its members as tellers. The tellers will use the list archive to tabulate the members' votes, using the OpenSTV application[2] configured to use the Meek and Warren STV method[3]. The tellers will report the election results, along with the raw tallies, at a special board meeting to be held on Tuesday, 2011-03-15, 15:00 UTC. - - After canvassing the results from the tellers, the board will notify all nominees of the success / failure of their candidacy, thanking them for their willingness to serve. - - At the general meeting, the last item on the agenda will the announcement of the election results, including a vote to seat the board. An online version of this announcement is available at: http://foundation.zope.org/news/2011_election_and_general_meeting/ References - -- [1] http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf [2] http://stv.sourceforge.net/aboutopenstv [3] http://stv.sourceforge.net/votingmethods/meek Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1B8owACgkQ+gerLs4ltQ7OaACfSBCwcbLsELAk/n9eW0CblmMz UvcAn0a1hIhLiocRo8GG431ccPnzDK7/ =2p6F -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-CMF] SVN: Products.CMFCore/branches/2.2/Products/CMFCore/exportimport/content.py remove type check that seem useless
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/13/2011 11:03 AM, Godefroid Chapelle wrote: Le 13/01/11 15:04, Tres Seaver a écrit : This change should be reverted -- you now double-encode any already-encoded UTF=8 strings. We should probably add a test for that condition. Change reverted, test added in 119566. Merci beaucoup! Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0vJM0ACgkQ+gerLs4ltQ6lgwCgmnZqUQ2SPfIvFJBelAd6fVOV RaUAnR11jpd4fPu2ixHYo5/N9ctOfLmV =SrV8 -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-dev] Zope 2: specifying Zope2 dependency
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/11/2011 02:05 PM, Hanno Schlichting wrote: On Tue, Jan 11, 2011 at 7:58 PM, Charlie Clark charlie.cl...@clark-consulting.eu wrote: Am 04.01.2011, 14:25 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu: With the current roadmap, we'll likely be able to stop using Zope 2.12 in 6-9 months altogether. I've given this some thought: as long as Python 2.5 is the default install on Debian-based systems, as it currently is, you can't really go beyond Zope 2.12. This was the reason why support for Python 2.5 wasn't dropped for the ZTK 1 Python 2.5 isn't supported by Zope 2.12 either (it is by ZTK 1.0 and 1.1). In fact there's no currently supported Zope 2 release that supports Python 2.5 (apart from the volunteer security support for 2.11/2.10 by some community members). And it's not only missing support claims, the code just doesn't work anymore in all cases. In all the hosting environments where we use Debian, we installed backports of Python 2.6. That's the price you pay for using a very stable distro for fast moving web stuff. Python 2.5 isn't even getting security fixes from Python devs now, which means that Debian users are holding more risk than they know (I strongly doubt the Debian packagers of Python are up for backporting all the potential security fixes in the 2.6 / 2.7 lines). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0sz1IACgkQ+gerLs4ltQ66dACgr0wF+fIm4yAKEY1GGvTAS8Kz jMwAoJDrVN/vPUIcJT/oimsMUm5satGA =lND0 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 67 OK, 2 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2011 06:58 AM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Fri Jan 7 12:00:00 2011 UTC to Sat Jan 8 12:00:00 2011 UTC. There were 69 messages: 8 from Zope Tests, 2 from buildbot at pov.lt, 8 from ccomb at free.fr, 51 from jdriessen at thehealthagency.com. Unknown --- Subject: UNKNOWN : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Sat Jan 8 01:19:40 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/028216.html Subject: UNKNOWN : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Sat Jan 8 01:21:40 EST 2011 URL: http://mail.zope.org/pipermail/zope-tests/2011-January/028217.html These both look like: Running /usr/local/python2.6/bin/python ./bin/test --all Traceback (most recent call last): File ./bin/test, line 23, in module import zope.testrunner ImportError: No module named zope.testrunner The buildout output looks normal to me -- I'm not sure how to diagnose remotely. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0om78ACgkQ+gerLs4ltQ5fkwCfXY49zmhiS7H6UqyUp9w9sqZd IkoAnit6zKeDb3UvcBZgkin1spzZ4nNm =MTVA -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] Monkey patch for BLOB support in OFS.Image Images and Files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/08/2011 05:58 AM, Jens Vagelpohl wrote: On 1/7/11 22:28 , William Heymann wrote: I have a monkey patch here that I would like comments on it and to see how it works for others. Hi William, A huge monkey patch like that makes it very hard to compare it with the original implementation and see the actual changes. You could help the review *greatly* by providing a diff to the original implementation instead, and post that to the Zope bug tracker on Launchpad: https://bugs.launchpad.net/zope2 The developer docs help explain how to create such a patch as a non-committer: in particular: http://docs.zope.org/developer/noncommitter-svn.html shows how to use SVN to generate the patch without needing write access. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0omvYACgkQ+gerLs4ltQ5aLACeJTsnaKuyRAi6uEnFePwBR+eP YzgAn1P7M20BpM2/H5JncUFv7QLhCgSZ =Xfvp -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] Zope Tests: 67 OK, 8 Failed, 2 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/06/2011 12:19 PM, Gediminas Paulauskas wrote: I don't see any reason why zope.html 2.2.0 would fail on python2.4. The changes were minimal, only version and email changed in setup.py, but because of some bug in python2.4 this archive is not fully extracted. SchoolTool buildbots were green after update to zope.html 2.2.0, so I thought that was safe. But they only run python2.6 and 2.5. Sorry for the breakage. Hmm, I wonder if it was this bug: http://bugs.python.org/issue1719898 (the old '/' at the 100th character in a filename trick). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0mXnwACgkQ+gerLs4ltQ47mACdFX9AcYynRSVR9l/0oEU9YU7i DbQAoNMKGkeEvPRj4tgO9dSsGnaa4cL+ =1NN5 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope] Trouble getting Zope 2.8/Python 2.3 to work in OS X 10.6
, render_blocks, str File /opt/local/libexec/Zope/lib/python/DocumentTemplate/ DT_Util.py, line 19, in module from html_quote import html_quote, ustr # for import by other modules, dont remove! File /opt/local/libexec/Zope/lib/python/DocumentTemplate/ html_quote.py, line 4, in module from ustr import ustr File /opt/local/libexec/Zope/lib/python/DocumentTemplate/ustr.py, line 18, in module nasty_exception_str = Exception.__str__.im_func AttributeError: 'wrapper_descriptor' object has no attribute 'im_func' Does this make sense to anyone? Has anyone had any luck with Macports (using zope) under os x 10.6 (Snow Leopard?) I think you must be running with a much-too-recent version of Python. Quoting the 'doc/INSTALL.txt' from the 2.8 branch:: - % --- System requirements when building from source bash or another Bourne shell variant Python 2.3.5 or later installed somewhere in the system PATH (Note: Python 2.4 is officially *not* supported because there has not been a security audit for Python 2.4 and Zope 2 so far. If you use Python 2.4 with Zope then you use it at your own risk from the security perspective). GNU make A C compiler (gcc recommended) - % -- Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0mXbkACgkQ+gerLs4ltQ5FPACeLhwmwIOiHyafy3DyHAhPVVMz WXAAmwcBCpYwlSa60wEr6QhiQn+Wd4yT =xLZZ -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-dev] Zope 2: specifying Zope2 dependency
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/04/2011 02:24 PM, William Heymann wrote: On Tuesday 04 January 2011, yuppie wrote: Zope trunk (2.14) no longer ships with these Products: Products.BTreeFolder2 Products.ExternalMethod Products.MailHost Products.MIMETools Products.PythonScripts Products.StandardCacheManagers What will this mean for those of us that don't use plone and use all of the above products? Will these products continue to be maintained in some way or are they being abandoned? If they are being abandoned is there any upgrade path? They aren't abandoned -- they are being maintained as separately-releasd projects. If your applications depend on one or more of them, you just add them to your 'install_requires' when you port to Zope = 2.13. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0jhHsACgkQ+gerLs4ltQ6sgQCbBEkstcadqyWV2FkGldvEensh Ni8An0f1JAvZ0ajOLTHhh98lR68c/bA2 =BdNi -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 45 OK, 9 Failed, 1 Unknown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Thu Dec 30 10:37:03 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027612.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Thu Dec 30 10:41:00 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027614.html ... Subject: FAILED : Zope Buildbot / zope2.13-py2.6 slave-osx From: jdriessen at thehealthagency.com Date: Thu Dec 30 11:16:16 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027629.html Hmm, these look like genuine issues, either with the tests or perhaps with the new lazy stuff: - -- % --- Failure in test test_length_with_filter (Products.ZCatalog.tests.test_lazy.TestLazyFilter) Traceback (most recent call last): File C:\Python26\lib\unittest.py, line 279, in run testMethod() File c:\users\richard\.buildout\eggs\products.zcatalog-2.13.1-py2.6.egg\Products\ZCatalog\tests\test_lazy.py, line 153, in test_length_with_filter self.assertEqual(len(lfilter), 26) File C:\Python26\lib\unittest.py, line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: 65 != 26 Failure in test test_length_with_filter (Products.ZCatalog.tests.test_lazy.TestLazyMop) Traceback (most recent call last): File C:\Python26\lib\unittest.py, line 279, in run testMethod() File c:\users\richard\.buildout\eggs\products.zcatalog-2.13.1-py2.6.egg\Products\ZCatalog\tests\test_lazy.py, line 201, in test_length_with_filter self.assertEqual(len(lmop), 52) File C:\Python26\lib\unittest.py, line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: 125 != 52 - -- % --- Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0d8lkACgkQ+gerLs4ltQ6viACgh8HcKqJg/ejJj2RonBg6bDJL fyMAoI76P6aTh8bIKKBpzxMlBXLiTi3k =Wlhg -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 30 OK, 19 Failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/30/2010 06:58 AM, Zope Tests Summarizer wrote: Summary of messages to the zope-tests list. Period Wed Dec 29 12:00:00 2010 UTC to Thu Dec 30 12:00:00 2010 UTC. There were 49 messages: 8 from Zope Tests, 2 from buildbot at pov.lt, 8 from ccomb at free.fr, 31 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 09:52:19 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027555.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 09:56:39 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027556.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 11:21:24 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027557.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 11:21:37 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027558.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 11:21:48 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027559.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 11:39:02 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027560.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 11:54:14 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027562.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 12:01:59 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027563.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 12:09:08 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027564.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 12:18:30 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027565.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 12:31:31 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027566.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 12:43:34 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027568.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 19:44:14 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027579.html Subject: FAILED : Zope Buildbot / zope2.13_win-py2.7 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 19:45:08 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027580.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.4 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 19:52:25 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027581.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 19:58:49 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027582.html Subject: FAILED : Zope Buildbot / zopetoolkit-1.0_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 20:01:12 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027583.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.5 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 20:09:54 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027584.html Subject: FAILED : Zope Buildbot / zopetoolkit_win-py2.6 slave-win From: jdriessen at thehealthagency.com Date: Wed Dec 29 20:10:09 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027585.html I didn't look at all of them, but at least some failures are due to borked filesystem permissions:: WindowsError: [Error 5] Access is denied: 'c:\\windows\\temp/*.*' While: Installing. Processing develop directory 'C:\\Users\\richard\\Desktop\\buildslave\\zope2.13_win-py2.6_slave-win\\build\\.'. Tres. - -- === Tres Seaver +1 540-429-0999 tsea
Re: [Zope-dev] Zope Tests: 30 OK
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 GOOAL! - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk0UrncACgkQ+gerLs4ltQ65WQCgo85+1BZvu5adstHv+ktBIgPQ CmQAn3X8JjG6uR1TerSCoEiAhVL+k/Ew =vnHT -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 29 OK, 1 Unknown
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/23/2010 06:58 AM, Zope Tests Summarizer wrote:
Summary of messages to the zope-tests list.
Period Wed Dec 22 12:00:00 2010 UTC to Thu Dec 23 12:00:00 2010 UTC.
There were 30 messages: 8 from Zope Tests, 4 from buildbot at pov.lt, 8 from
ccomb at free.fr, 10 from jdriessen at thehealthagency.com.
Unknown
---
Subject: UNKNOWN : Zope-2.12-alltests Python-2.6.5 : Linux
From: Zope Tests
Date: Thu Dec 23 01:07:31 EST 2010
URL: http://mail.zope.org/pipermail/zope-tests/2010-December/027248.html
We're really close to all green here: down to one networing failure
during buildout:
Running /usr/local/python2.6/bin/python bootstrap.py
Traceback (most recent call last):
File bootstrap.py, line 74, in module
exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py'
...
urllib2.URLError: urlopen error [Errno 113] No route to host
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0TUYAACgkQ+gerLs4ltQ5MjACguOi9hakxe7oKeDvAF0coqVlW
Y+4An1vH5QKUWhWZxOljIUNa5OC2SKiE
=BS/o
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
