March 2013 - Zope-Dev

zope-tests - FAILED: 10, OK: 12
by Zope tests summarizer 15 Mar '13

15 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-13 00:00:00 UTC and 2013-03-14 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 ---------------- [1] Still Failing - zopetoolkit_trunk - Build # 202 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.form_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [5] winbot / z3c.layer.ready2go_py_265_32 [6] winbot / z3c.pagelet_py_265_32 [7] winbot / zope.app.localpermission_py_265_32 [8] winbot / zope.app.wsgi_py_265_32 [9] winbot / zope.site_py_265_32 [10] winbot / zope.viewlet_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 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 202 https://mail.zope.org/pipermail/zope-tests/2013-March/073325.html [2] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073339.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073318.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073321.html [5] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073319.html [6] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073320.html [7] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073324.html [8] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073338.html [9] FAILED winbot / zope.site_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073323.html [10] FAILED winbot / zope.viewlet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073322.html

3 3

Problems writing ContainedProxy Python version
by Stephan Richter 15 Mar '13

15 Mar '13

Hi everyone, in an effort to bring zope.container to PyPy, I was trying to port zope.container. Unfortunately, it defines a ContainedProxy, which inherits from zope.security's PyProxyBase and persistent's ProxyPy. Since both of those proxies have slots defined, they cannot both be base classes for the ContainedProxy. So what should I do? I could split the existing classes like so, but it seems ugly: class BaseProxyPy(object): ... class ProxyPy(BaseProxyPy) __slots__ = ('_wrapped',) Jim, Tres, any ideas/comments? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

1 0

zope-tests - FAILED: 6, OK: 12
by Zope tests summarizer 15 Mar '13

15 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-12 00:00:00 UTC and 2013-03-13 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 ---------------- [1] Still Failing - zopetoolkit_trunk - Build # 201 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.contents_py_265_32 [3] winbot / zope.app.applicationcontrol_py_265_32 [4] winbot / zope.app.content_py_265_32 [5] winbot / zope.app.pagetemplate_py_265_32 [6] winbot / zope.app.wsgi_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 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 201 https://mail.zope.org/pipermail/zope-tests/2013-March/073303.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073316.html [3] FAILED winbot / zope.app.applicationcontrol_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073301.html [4] FAILED winbot / zope.app.content_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073302.html [5] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073300.html [6] FAILED winbot / zope.app.wsgi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073317.html

3 2

Version Numbering for Ported Packages
by Stephan Richter 14 Mar '13

14 Mar '13

Hi everyone, Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres wanted 4.0.0 to also have PyPy support, so he only did an alpha release to unblock the porting effort. Today, I finished the PyPy support and he released 4.0.0b1. * ZODB: We currently do not have a release for a ported ZODB. For any package requiring the ZODB directly or indirectly, we added a snapshot sdist of the py3 branch into the package to demonstrate the tests passing. (See the zodb- dev mailing list for the current status.) Of course, the alpha releases are really stable, all the tests pass under Python 2.6 and 2.7. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

3 8

Confirmation email message after adding a new user
by Murat Bilal 14 Mar '13

14 Mar '13

Hi, I want to change the confirmation email message after adding a new user in a plone site. >From where i can edit this confirmation email message. Thanks Murat

2 1

Github tip to get less github spam:
by Jim Fulton 13 Mar '13

13 Mar '13

Visit: https://github.com/watching Either unwatch all or selectively unwatch repositories you're not interested in. (If you stop watching all, there's a lot of clicking to then watch repositories again.) Uncheck autowatch (I wish I'd done this a couple of weekes ago :) Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton Jerky is better than bacon! http://zo.pe/Kqm

2 1

zope-tests - FAILED: 56, OK: 12
by Zope tests summarizer 13 Mar '13

13 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-11 00:00:00 UTC and 2013-03-12 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 ---------------- [1] Still Failing - zopetoolkit_trunk - Build # 200 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.baseregistry_py_265_32 [3] winbot / z3c.contents_py_265_32 [4] winbot / z3c.contents_py_265_32 [5] winbot / z3c.form_py_265_32 [6] winbot / z3c.formui_py_265_32 [7] winbot / z3c.formui_py_265_32 [8] winbot / z3c.json_py_265_32 [9] winbot / z3c.jsonrpc_py_265_32 [10] winbot / z3c.jsonrpcproxy_py_265_32 [11] winbot / z3c.jsontree_py_265_32 [12] winbot / z3c.language.negotiator_py_265_32 [13] winbot / z3c.language.session_py_265_32 [14] winbot / z3c.language.switch_py_265_32 [15] winbot / z3c.layer.ready2go_py_265_32 [16] winbot / z3c.layer.ready2go_py_265_32 [17] winbot / z3c.pagelet_py_265_32 [18] winbot / z3c.pagelet_py_265_32 [19] winbot / z3c.pdftemplate_py_265_32 [20] winbot / z3c.recipe.paster_py_265_32 [21] winbot / z3c.tabular_py_265_32 [22] winbot / z3c.viewtemplate_py_265_32 [23] winbot / z3c.xmlhttp_py_265_32 [24] winbot / z3c.zrtresource_py_265_32 [25] winbot / zc.i18n_py_265_32 [26] winbot / zc.monitor_py_265_32 [27] winbot / zc.ngi_py_265_32 [28] winbot / zc.resourcelibrary_py_265_32 [29] winbot / zc.table_py_265_32 [30] winbot / zope.app.authentication_py_265_32 [31] winbot / zope.app.basicskin_py_265_32 [32] winbot / zope.app.broken_py_265_32 [33] winbot / zope.app.component_py_265_32 [34] winbot / zope.app.container_py_265_32 [35] winbot / zope.app.debug_py_265_32 [36] winbot / zope.app.dependable_py_265_32 [37] winbot / zope.app.error_py_265_32 [38] winbot / zope.app.exception_py_265_32 [39] winbot / zope.app.folder_py_265_32 [40] winbot / zope.app.form_py_265_32 [41] winbot / zope.app.generations_py_265_32 [42] winbot / zope.app.http_py_265_32 [43] winbot / zope.app.i18n_py_265_32 [44] winbot / zope.app.interface_py_265_32 [45] winbot / zope.app.locales_py_265_32 [46] winbot / zope.app.localpermission_py_265_32 [47] winbot / zope.app.principalannotation_py_265_32 [48] winbot / zope.app.publication_py_265_32 [49] winbot / zope.app.publisher_py_265_32 [50] winbot / zope.app.rotterdam_py_265_32 [51] winbot / zope.app.schema_py_265_32 [52] winbot / zope.app.security_py_265_32 [53] winbot / zope.app.session_py_265_32 [54] winbot / zope.app.testing_py_265_32 [55] winbot / zope.app.zcmlfiles_py_265_32 [56] winbot / zope.app.zopeappgenerations_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 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 200 https://mail.zope.org/pipermail/zope-tests/2013-March/073236.html [2] FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073254.html [3] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073294.html [4] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073235.html [5] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073279.html [6] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073290.html [7] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073234.html [8] FAILED winbot / z3c.json_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073298.html [9] FAILED winbot / z3c.jsonrpc_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073278.html [10] FAILED winbot / z3c.jsonrpcproxy_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073252.html [11] FAILED winbot / z3c.jsontree_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073280.html [12] FAILED winbot / z3c.language.negotiator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073284.html [13] FAILED winbot / z3c.language.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073251.html [14] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073297.html [15] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073283.html [16] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073232.html [17] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073287.html [18] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073233.html [19] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073272.html [20] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073261.html [21] FAILED winbot / z3c.tabular_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073259.html [22] FAILED winbot / z3c.viewtemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073257.html [23] FAILED winbot / z3c.xmlhttp_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073285.html [24] FAILED winbot / z3c.zrtresource_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073262.html [25] FAILED winbot / zc.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073296.html [26] FAILED winbot / zc.monitor_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073256.html [27] FAILED winbot / zc.ngi_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073250.html [28] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073267.html [29] FAILED winbot / zc.table_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073264.html [30] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073277.html [31] FAILED winbot / zope.app.basicskin_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073274.html [32] FAILED winbot / zope.app.broken_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073263.html [33] FAILED winbot / zope.app.component_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073288.html [34] FAILED winbot / zope.app.container_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073260.html [35] FAILED winbot / zope.app.debug_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073295.html [36] FAILED winbot / zope.app.dependable_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073275.html [37] FAILED winbot / zope.app.error_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073286.html [38] FAILED winbot / zope.app.exception_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073273.html [39] FAILED winbot / zope.app.folder_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073253.html [40] FAILED winbot / zope.app.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073282.html [41] FAILED winbot / zope.app.generations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073289.html [42] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073265.html [43] FAILED winbot / zope.app.i18n_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073258.html [44] FAILED winbot / zope.app.interface_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073270.html [45] FAILED winbot / zope.app.locales_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073266.html [46] FAILED winbot / zope.app.localpermission_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073269.html [47] FAILED winbot / zope.app.principalannotation_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073291.html [48] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073276.html [49] FAILED winbot / zope.app.publisher_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073268.html [50] FAILED winbot / zope.app.rotterdam_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073293.html [51] FAILED winbot / zope.app.schema_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073292.html [52] FAILED winbot / zope.app.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073281.html [53] FAILED winbot / zope.app.session_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073271.html [54] FAILED winbot / zope.app.testing_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073249.html [55] FAILED winbot / zope.app.zcmlfiles_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073255.html [56] FAILED winbot / zope.app.zopeappgenerations_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073299.html

2 1

Re: [Zope-dev] [zopefoundation/zope.security] 82fd54: Changed strategy to hide wrapped to not use the se...
by Tres Seaver 12 Mar '13

12 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/11/2013 11:33 AM, GitHub wrote: > Oh yeah, all tests pass now on py26, py27, py32, py33, and pypy! Woohoo! Nice work. BTW, how did you break the import cycle due to the zope.location monkeypatch? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlE9/poACgkQ+gerLs4ltQ41BgCggEXl0utNEQAydRv1rws1xPrt +28AoJZvfxTNgRvKBhHXstxxDvTzcurE =2XB9 -----END PGP SIGNATURE-----

3 7

zope-tests - FAILED: 10, OK: 12
by Zope tests summarizer 12 Mar '13

12 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-10 00:00:00 UTC and 2013-03-11 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 ---------------- [1] Still Failing - zopetoolkit_trunk - Build # 199 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [2] winbot / z3c.contents_py_265_32 [3] winbot / z3c.form_py_265_32 [4] winbot / z3c.formui_py_265_32 [5] winbot / z3c.layer.ready2go_py_265_32 [6] winbot / z3c.menu.ready2go_py_265_32 [7] winbot / z3c.pagelet_py_265_32 [8] winbot / zope.app.authentication_py_265_32 [9] winbot / zope.app.http_py_265_32 [10] winbot / zope.app.publication_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 Non-OK results -------------- [1] FAILED Still Failing - zopetoolkit_trunk - Build # 199 https://mail.zope.org/pipermail/zope-tests/2013-March/073214.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073213.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073230.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073212.html [5] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073210.html [6] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073231.html [7] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073211.html [8] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073229.html [9] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073227.html [10] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073228.html

2 2

zope generations updating objects with method name change
by Joshua Immanuel 12 Mar '13

12 Mar '13

Hello, My application is based on Grok. Whenver, I change a method-name or add a method to a Model, Grok fails to load the previous version from the ZODB. I resorted to writing simple generations (zope.generations) to update the stored model objects. For 'method name' changes, this basically means: 1. create new object 2. copy every single attribute of old-object to the new-object 3. delete old-object 4. save new-object How does everyone else do this? Or is there a way to make grok/zope/zodb not persist the method-names and signatures in a content component (grok Model)? -- Joshua Immanuel HiPro IT Solutions Private Limited http://hipro.co.in

2 2