Zope-Dev October 2011

zope-dev@zope.dev

29 participants
48 discussions

zope.sqlalchemy+py3 test failures.
by Chris McDonough 06 Dec '11

06 Dec '11

In case anyone is interested, I've made a stab at porting zope.sqlalchemy to Python 3 at http://svn.zope.org/zope.sqlalchemy/branches/chrism-py3/ . Several tests still fail. I could use some help fixing them. To run the test suite: - Create a Python 3.2 virtualenv. - Install nose into the virtualenv. - Check out the "chrism-py3" transaction branch from svn://svn.zope.org/repos/main/transaction/branches/chrism-py3 - Install the "chrism-py3" transaction checkout into the virtualenv, e.g. $env32/bin/python setup.py develop. - Install this package into the virtualenv eg. run $env32/bin/python setup develop. - Run $env32/bin/python setup.py nosetests. Currently 2 tests fail: [chrism@thinko zope.sqlalchemy]$ env32/bin/python setup.py test running test running egg_info writing requirements to src/zope.sqlalchemy.egg-info/requires.txt writing src/zope.sqlalchemy.egg-info/PKG-INFO writing namespace_packages to src/zope.sqlalchemy.egg-info/namespace_packages.txt writing top-level names to src/zope.sqlalchemy.egg-info/top_level.txt writing dependency_links to src/zope.sqlalchemy.egg-info/dependency_links.txt writing manifest file 'src/zope.sqlalchemy.egg-info/SOURCES.txt' running build_ext testTwoEngines (zope.sqlalchemy.tests.MultipleEngineTests) ... ok testRetry (zope.sqlalchemy.tests.RetryTests) ... ERROR testRetryThread (zope.sqlalchemy.tests.RetryTests) ... ERROR testAbortAfterCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testAbortBeforeCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testBulkDelete (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testBulkUpdate (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testCommit (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testCommitWithSavepoint (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testMarkUnknownSession (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testRelations (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testRollbackAttributes (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testSavepoint (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testSimplePopulation (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testThread (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testTransactionJoining (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok testTwoPhase (zope.sqlalchemy.tests.ZopeSQLAlchemyTests) ... ok ====================================================================== ERROR: testRetry (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1633, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/default.py", line 327, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: no such table: test_users The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 513, in setUp self.tm1.commit() File "/home/chrism/projects/transaction/transaction/_manager.py", line 89, in commit return self.get().commit() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 342, in commit reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 333, in commit self._commitResources() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 473, in _commitResources reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 445, in _commitResources rm.tpc_begin(self) File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/datamanager.py", line 87, in tpc_begin self.session.flush() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1493, in flush self._flush(objects) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1562, in _flush flush_context.execute() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 327, in execute rec.execute(self) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 471, in execute uow File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/mapper.py", line 2147, in _save_obj execute(statement, multiparams) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1399, in execute params) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1532, in _execute_clauseelement compiled_sql, distilled_params File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1640, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1777, in _handle_dbapi_exception from e sqlalchemy.exc.OperationalError: (OperationalError) no such table: test_users 'INSERT INTO test_users (id, firstname, lastname) VALUES (?, ?, ?)' (1, 'udo', 'juergens') ====================================================================== ERROR: testRetryThread (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1633, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/default.py", line 327, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: no such table: test_users The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 513, in setUp self.tm1.commit() File "/home/chrism/projects/transaction/transaction/_manager.py", line 89, in commit return self.get().commit() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 342, in commit reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 333, in commit self._commitResources() File "/home/chrism/projects/transaction/transaction/_transaction.py", line 473, in _commitResources reraise(t, v, tb) File "/home/chrism/projects/transaction/transaction/compat.py", line 60, in reraise raise value File "/home/chrism/projects/transaction/transaction/_transaction.py", line 445, in _commitResources rm.tpc_begin(self) File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/datamanager.py", line 87, in tpc_begin self.session.flush() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1493, in flush self._flush(objects) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/session.py", line 1562, in _flush flush_context.execute() File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 327, in execute rec.execute(self) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/unitofwork.py", line 471, in execute uow File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/orm/mapper.py", line 2147, in _save_obj execute(statement, multiparams) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1399, in execute params) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1532, in _execute_clauseelement compiled_sql, distilled_params File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1640, in _execute_context context) File "/home/chrism/projects/zope.sqlalchemy/env32/lib/python3.2/site-packages/SQLAlchemy-0.7.2-py3.2.egg/sqlalchemy/engine/base.py", line 1777, in _handle_dbapi_exception from e sqlalchemy.exc.OperationalError: (OperationalError) no such table: test_users 'INSERT INTO test_users (id, firstname, lastname) VALUES (?, ?, ?)' (1, 'udo', 'juergens') ---------------------------------------------------------------------- Ran 17 tests in 0.152s FAILED (errors=2) This appears to be some sort of Py3+SQLite thing, beacuse if I run the tests using Postgres isntead of SQLALchemy (after "env32/bin/easy_install py-postgresql", and then running the tests using 'TEST_DSN="postgresql+pypostgresql://localhost:5432/testing" env32/bin/python setup.py nosetests' against Postgres 8.4.8 after a "createdb testing"), I get different failures: ====================================================================== FAIL: testRetryThread (zope.sqlalchemy.tests.RetryTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/chrism/projects/zope.sqlalchemy/src/zope/sqlalchemy/tests.py", line 564, in testRetryThread self.assertTrue(retryable, "Error should be retryable") AssertionError: None is not true : Error should be retryable -------------------- >> begin captured logging << -------------------- txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: commit <zope.sqlalchemy.datamanager.SessionDataManager object at 0x2dd6ed0> txn.140333906949888: DEBUG: commit txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: commit <zope.sqlalchemy.datamanager.SessionDataManager object at 0x2dda9d0> txn.140333906949888: DEBUG: commit txn.140333906949888: DEBUG: new transaction txn.140333906949888: DEBUG: abort txn.140333906949888: DEBUG: abort --------------------- >> end captured logging << --------------------- ---------------------------------------------------------------------- Ran 18 tests in 5.099s FAILED (failures=1)

5 15

zope.schema and Python 3
by Brian Sutherland 08 Nov '11

08 Nov '11

I've managed to port zope.schema to Python 3.2 on a branch (jinty-python3). It gives up Python 2.5 compatibility and depends on six (http://packages.python.org/six/). Any objections to me merging this branch? -- Brian Sutherland

4 8

ZEO client cache not working properly with beforestorage
by Malthe Borch 07 Nov '11

07 Nov '11

If I set my beforestorage to a reasonably current time, e.g. "now", I expect to get reasonably good performance from a ZEO client cache. Instead, I find that beforestorage: 1) asks the cache to ``loadBefore``; 2) but that method only looks for "noncurrent" entries; 3) meanwhile, my cache only has "current" records. I'm not sure if the problem is that the cache shouldn't be setting the loaded oids as "current", or if the ``loadBefore`` method should also accept (some) "current" entries. \malthe

2 4

zope.testbrowser release?
by Wolfgang Schnerring 02 Nov '11

02 Nov '11

Hello, I've added an assertion helper to zope.testbrowser that provides ``assertEllipsis``, which is very helpful when using Testbrowser with unittest.TestCase (instead of doctests). Some examples: self.assertEllipsis('...bar...', 'foo bar qux') # -> nothing happens self.assertEllipsis('foo', 'bar') # -> AssertionError: Differences (ndiff with -expected +actual): - foo + bar self.assertNotEllipsis('foo', 'foo') # -> AssertionError: "Value unexpectedly matches expression 'foo'." For convenience, if no ``actual`` value is provided, ``self.browser.contents`` is used. I'd like to cut a release of zope.testbrowser, if nobody has any objections against my doing so. There are also unreleased changelog entries about handleErrors and WSGI, which look fine to me. Wolfgang -- Wolfgang Schnerring · ws(a)gocept.com · software development gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 219401 0 · fax +49 345 1229889 1 Python, Pyramid, Plone, Zope - consulting, development, hosting

2 3

zope-tests - FAILED: 13, OK: 40
by Zope tests summarizer 01 Nov '11

01 Nov '11

This is the summary for test reports received on the zope-tests list between 2011-10-29 00:00:00 UTC and 2011-10-30 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux [1] Repository policy check found errors in 300 projects [2] Total languishing bugs for zope2: 4 [3] Total languishing bugs for zope: 69 [4] Total languishing bugs for zopeapp: 2 [5] Total languishing bugs for zopetoolkit: 205 ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit ZTK 1.0 / Python2.6.7 Linux 64bit [6] ZTK 1.0dev / Python2.4.6 Linux 64bit [7] ZTK 1.0dev / Python2.5.5 Linux 64bit [8] ZTK 1.0dev / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.5.5 Linux 64bit ZTK 1.1 / Python2.6.7 Linux 64bit ZTK 1.1 / Python2.7.2 Linux 64bit [9] ZTK 1.1dev / Python2.5.5 Linux 64bit [10] ZTK 1.1dev / Python2.6.7 Linux 64bit [11] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [12] winbot / z3c.form_py_265_32 [13] winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED Repository policy check found errors in 300 projects https://mail.zope.org/pipermail/zope-tests/2011-October/051932.html [2] FAILED Total languishing bugs for zope2: 4 https://mail.zope.org/pipermail/zope-tests/2011-October/051928.html [3] FAILED Total languishing bugs for zope: 69 https://mail.zope.org/pipermail/zope-tests/2011-October/051927.html [4] FAILED Total languishing bugs for zopeapp: 2 https://mail.zope.org/pipermail/zope-tests/2011-October/051925.html [5] FAILED Total languishing bugs for zopetoolkit: 205 https://mail.zope.org/pipermail/zope-tests/2011-October/051926.html [6] FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051945.html [7] FAILED ZTK 1.0dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051946.html [8] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051948.html [9] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051944.html [10] FAILED ZTK 1.1dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051943.html [11] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051942.html [12] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051936.html [13] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051935.html

5 7

zope-tests - FAILED: 10, OK: 37
by Zope tests summarizer 31 Oct '11

31 Oct '11

This is the summary for test reports received on the zope-tests list between 2011-10-27 00:00:00 UTC and 2011-10-28 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Bluebream / Python2.5.5 64bit linux [1] Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [2] ZTK 1.0 / Python2.6.7 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit [3] ZTK 1.0dev / Python2.6.7 Linux 64bit [4] ZTK 1.1 / Python2.5.5 Linux 64bit [5] ZTK 1.1 / Python2.6.7 Linux 64bit [6] ZTK 1.1 / Python2.7.2 Linux 64bit [7] ZTK 1.1dev / Python2.5.5 Linux 64bit [8] ZTK 1.1dev / Python2.6.7 Linux 64bit [9] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [10] winbot / zope.dublincore_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED Bluebream / Python2.6.7 64bit linux https://mail.zope.org/pipermail/zope-tests/2011-October/051837.html [2] FAILED ZTK 1.0 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051875.html [3] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051846.html [4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051877.html [5] FAILED ZTK 1.1 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051874.html [6] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051876.html [7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051845.html [8] FAILED ZTK 1.1dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051842.html [9] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051844.html [10] FAILED winbot / zope.dublincore_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051843.html

3 3

zope-tests - FAILED: 9, OK: 37
by Zope tests summarizer 30 Oct '11

30 Oct '11

This is the summary for test reports received on the zope-tests list between 2011-10-26 00:00:00 UTC and 2011-10-27 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Bluebream / Python2.5.5 64bit linux [1] Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [2] ZTK 1.0 / Python2.6.7 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit [3] ZTK 1.0dev / Python2.6.7 Linux 64bit [4] ZTK 1.1 / Python2.5.5 Linux 64bit [5] ZTK 1.1 / Python2.6.7 Linux 64bit [6] ZTK 1.1 / Python2.7.2 Linux 64bit [7] ZTK 1.1dev / Python2.5.5 Linux 64bit [8] ZTK 1.1dev / Python2.6.7 Linux 64bit [9] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED Bluebream / Python2.6.7 64bit linux https://mail.zope.org/pipermail/zope-tests/2011-October/051792.html [2] FAILED ZTK 1.0 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051828.html [3] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051799.html [4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051830.html [5] FAILED ZTK 1.1 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051827.html [6] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051829.html [7] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051798.html [8] FAILED ZTK 1.1dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051790.html [9] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051797.html

3 4

zope-tests - FAILED: 11, OK: 35
by Zope tests summarizer 30 Oct '11

30 Oct '11

This is the summary for test reports received on the zope-tests list between 2011-10-28 00:00:00 UTC and 2011-10-29 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Bluebream / Python2.5.5 64bit linux [1] Bluebream / Python2.6.7 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit [2] ZTK 1.0 / Python2.5.5 Linux 64bit [3] ZTK 1.0 / Python2.6.7 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit [4] ZTK 1.0dev / Python2.6.7 Linux 64bit [5] ZTK 1.1 / Python2.5.5 Linux 64bit [6] ZTK 1.1 / Python2.6.7 Linux 64bit [7] ZTK 1.1 / Python2.7.2 Linux 64bit [8] ZTK 1.1dev / Python2.5.5 Linux 64bit [9] ZTK 1.1dev / Python2.6.7 Linux 64bit [10] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 winbot / ztk_10 py_254_win32 [11] winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED Bluebream / Python2.6.7 64bit linux https://mail.zope.org/pipermail/zope-tests/2011-October/051884.html [2] FAILED ZTK 1.0 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051879.html [3] FAILED ZTK 1.0 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051921.html [4] FAILED ZTK 1.0dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051892.html [5] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051923.html [6] FAILED ZTK 1.1 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051920.html [7] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051922.html [8] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051891.html [9] FAILED ZTK 1.1dev / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051889.html [10] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051890.html [11] FAILED winbot / ztk_10 py_265_win32 https://mail.zope.org/pipermail/zope-tests/2011-October/051911.html

1 0

Zope 4 publisher/traversal, sprint topic
by Leonardo Rochael Almeida 28 Oct '11

28 Oct '11

Hi, Sorry for the cross-post, but I'd like to talk about a possible sprint topic for the next DZUG sprint[1], and invite myself to it :-) After the last two rather serious security issues that were recently patched in the Zope2 code base, it is increasingly clear to me that, differently than what Hanno reported some time ago, it's not so much the ZMI that represents a huge security liability in the Zope codebase, but it's actually the way the current publisher happily traverses any attribute and publishes any method with docstring by default. The ZMI, of course, has its problems (ugly in appearance and even uglier in code), and I agree with Hanno on most everything he has to say about it, but I'd like to propose we start, for Zope 4, by tackling the potential security liability that is the Zope publisher itself, and the fact that it makes it easy to open up large security holes if you're not paying attention. I'd like to propose that publishing traversal in Zope 4 would, by default only traverse based on __getitem__ (not attribute lookup). For a minimum of backward compatibility, it could perhaps do a single traversal on getattr, and only after it has exhausted __getitem__ traversal. After this, if the traversal found something, it would only be published if there is an explicit indication of intention that the object in question is supposed to be published. Otherwise, raise a NotFound, as if the traversal had failed. One example of an explicit demonstration of intent is, for example, if it provides an IPublishable interface (I just made that up, other names can be considered). Taking a suggestion from Shane, we could have convenient decorators for people who wants to explicitly publish class methods. They could dynamically create ZTK views with the same name as the function that they wrap and allow (or perhaps enable by default) some form of CSRF protection. To ease code migration, we could consider that the InitializeClass call provides the same effect as the above decorator. This would allow large amounts of previously existing code to work without recoding, while at the same time avoiding the security trap of forgetting to call InitializeClass and thus exposing unintented methods. It could even remove the need for the "single getattr traversal" compatibility above. On top of that, if InitializeClass register these views to a specific ZTK "skin", it would make it possible to disable them by default, unless that specific skin is in effect, which would alleviate what Hanno described as "running phpMyAdmin accessible to the world with the same credentials and on the same domain as the rest of your application". Anyway, I think the above is on-topic for the next DZUG sprint and I'd like to work on it there. So, even if the sprint is supposed to be in German, and I don't speak a word of it, can I attend? [1] http://www.zope.de/community/veranstaltungen/3.-dzug-sprint-2011-zmi , translation at: http://translate.google.com/translate?hl=en&sl=auto&tl=en&u=http%3A%2F%2Fww… Cheers, Leo

7 6

zope-tests - FAILED: 12, OK: 39
by Zope tests summarizer 27 Oct '11

27 Oct '11

This is the summary for test reports received on the zope-tests list between 2011-10-25 00:00:00 UTC and 2011-10-26 00:00:00 UTC: See the footnotes for test reports of unsuccessful builds. An up-to date view of the builders is also available in our buildbot documentation: http://docs.zope.org/zopetoolkit/process/buildbots.html#the-nightly-builds Reports received ---------------- Bluebream / Python2.5.5 64bit linux Bluebream / Python2.6.5 64bit linux Bluebream / Python2.7.2 64bit linux ZTK 1.0 / Python2.4.6 Linux 64bit ZTK 1.0 / Python2.5.5 Linux 64bit [1] ZTK 1.0 / Python2.6.5 Linux 64bit [2] ZTK 1.0 / Python2.6.7 Linux 64bit ZTK 1.0dev / Python2.4.6 Linux 64bit ZTK 1.0dev / Python2.5.5 Linux 64bit ZTK 1.0dev / Python2.6.5 Linux 64bit [3] ZTK 1.1 / Python2.5.5 Linux 64bit [4] ZTK 1.1 / Python2.5.5 Linux 64bit [5] ZTK 1.1 / Python2.6.5 Linux 64bit [6] ZTK 1.1 / Python2.6.7 Linux 64bit [7] ZTK 1.1 / Python2.7.2 Linux 64bit [8] ZTK 1.1 / Python2.7.2 Linux 64bit [9] ZTK 1.1dev / Python2.5.5 Linux 64bit [10] ZTK 1.1dev / Python2.6.5 Linux 64bit [11] ZTK 1.1dev / Python2.7.2 Linux 64bit Zope 3.4 KGS / Python2.4.6 64bit linux Zope 3.4 KGS / Python2.5.5 64bit linux Zope 3.4 Known Good Set / py2.4-32bit-linux Zope 3.4 Known Good Set / py2.4-64bit-linux Zope 3.4 Known Good Set / py2.5-32bit-linux Zope 3.4 Known Good Set / py2.5-64bit-linux Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.6 : Linux Zope-2.12-alltests Python-2.6.6 : Linux Zope-2.13 Python-2.6.6 : Linux Zope-2.13-alltests Python-2.6.6 : Linux Zope-trunk Python-2.6.6 : Linux Zope-trunk-alltests Python-2.6.6 : Linux winbot / ZODB_dev py_254_win32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [12] winbot / z3c.form_py_265_32 winbot / ztk_10 py_254_win32 winbot / ztk_10 py_265_win32 winbot / ztk_10 py_265_win64 winbot / ztk_11 py_254_win32 winbot / ztk_11 py_265_win32 winbot / ztk_11 py_265_win64 winbot / ztk_11 py_270_win32 winbot / ztk_11 py_270_win64 winbot / ztk_dev py_265_win32 winbot / ztk_dev py_265_win64 winbot / ztk_dev py_270_win32 winbot / ztk_dev py_270_win64 Non-OK results -------------- [1] FAILED ZTK 1.0 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051738.html [2] FAILED ZTK 1.0 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051782.html [3] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051784.html [4] FAILED ZTK 1.1 / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051736.html [5] FAILED ZTK 1.1 / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051735.html [6] FAILED ZTK 1.1 / Python2.6.7 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051781.html [7] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051783.html [8] FAILED ZTK 1.1 / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051734.html [9] FAILED ZTK 1.1dev / Python2.5.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051751.html [10] FAILED ZTK 1.1dev / Python2.6.5 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051749.html [11] FAILED ZTK 1.1dev / Python2.7.2 Linux 64bit https://mail.zope.org/pipermail/zope-tests/2011-October/051750.html [12] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2011-October/051752.html

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev October 2011