March 2013 - Zope-Dev

zam.demo fixed
by Christopher Lozinski 11 Mar '13

11 Mar '13

The bug was that the included bootstrap.py did not work. If you use the bootstrap.py from the zam.demo svn directory it does not start. I used a more recent bootstrap.py copied from my ztfy directory, thank You Thierry, and it starts fine. It looks gorgeous. Thanks to all the authors who put in all that hard work. srichter, icemac, rogerineichen et al. I presume that this is the right place to report that bug. And the fix! You can take a look at zam.demo running at demo.zopache.org:8080 User:Manager Password: password Here is the high level zam.demo documentation which I am updating. http://wiki.zopache.org/ZamDocumentation And here is a copy of the low level file system documentation wiki.zopache.org/ZAM That is easier to access than digging through the file system. ZAM provides a large part of what I need for a TTW development environment. Sadly its navigation view, the one that should implement listing objects in a folder, adding, renaming, deleting, and exporting them has not been implemented. The page template file in zam.skin is empty. For that functionality I can use ZMI. So I need to first get ZMI working with ZAM, and then copy over some of the ZMI source code to zam.skin. It is not so easy. ZAM uses an older release of ZTK, from two years ago. Specifically it uses a different version of ZCA interface than ZTFY uses. So I cannot add zam.demo to ZTFY. Going the other way, ZAM does not have a setup.py file. How is that possible? I thought setup.py did a whole bunch of important things. Do I go ahead and update the buildout.cfg file with the zmi? , or do I redo the zam.demo installation scripts to use a setup.py file? What I really need to do is hire a senior ztk developer to provide me with high level guidance. Anyone interested? Regards Chris

1 0

zope-tests - FAILED: 14, OK: 13
by Zope tests summarizer 11 Mar '13

11 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-09 00:00:00 UTC and 2013-03-10 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] Repository policy check found errors in 446 projects [2] Still Failing - zopetoolkit_trunk - Build # 198 Total languishing bugs for zope2: 0 [3] Total languishing bugs for zope: 66 [4] Total languishing bugs for zopeapp: 1 [5] Total languishing bugs for zopetoolkit: 184 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [6] winbot / z3c.contents_py_265_32 [7] winbot / z3c.form_py_265_32 [8] winbot / z3c.formui_py_265_32 [9] winbot / z3c.layer.ready2go_py_265_32 [10] winbot / z3c.menu.ready2go_py_265_32 [11] winbot / z3c.pagelet_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.http_py_265_32 [14] 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 Repository policy check found errors in 446 projects https://mail.zope.org/pipermail/zope-tests/2013-March/073191.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 198 https://mail.zope.org/pipermail/zope-tests/2013-March/073192.html [3] FAILED Total languishing bugs for zope: 66 https://mail.zope.org/pipermail/zope-tests/2013-March/073189.html [4] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2013-March/073187.html [5] FAILED Total languishing bugs for zopetoolkit: 184 https://mail.zope.org/pipermail/zope-tests/2013-March/073188.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073186.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073208.html [8] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073185.html [9] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073183.html [10] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073209.html [11] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073184.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073207.html [13] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073205.html [14] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073206.html

1 0

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

10 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-08 00:00:00 UTC and 2013-03-09 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 # 197 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.form_py_265_32 [5] winbot / z3c.formui_py_265_32 [6] winbot / z3c.layer.ready2go_py_265_32 [7] winbot / z3c.menu.ready2go_py_265_32 [8] winbot / z3c.menu.ready2go_py_265_32 [9] winbot / z3c.pagelet_py_265_32 [10] winbot / zope.app.authentication_py_265_32 [11] winbot / zope.app.http_py_265_32 [12] 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 # 197 https://mail.zope.org/pipermail/zope-tests/2013-March/073165.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073164.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073181.html [4] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073159.html [5] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073163.html [6] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073161.html [7] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073182.html [8] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073160.html [9] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073162.html [10] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073180.html [11] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073178.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073179.html

1 0

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

09 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-07 00:00:00 UTC and 2013-03-08 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 # 195 [2] Still Failing - zopetoolkit_trunk - Build # 196 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [3] winbot / z3c.contents_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.authentication_py_265_32 [8] winbot / zope.app.http_py_265_32 [9] winbot / zope.app.publication_py_265_32 [10] winbot / zope.app.renderer_py_265_32 [11] winbot / zope.security_py_265_32 [12] 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 # 195 https://mail.zope.org/pipermail/zope-tests/2013-March/073142.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 196 https://mail.zope.org/pipermail/zope-tests/2013-March/073143.html [3] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073140.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073139.html [5] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073136.html [6] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073137.html [7] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073158.html [8] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073156.html [9] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073157.html [10] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073138.html [11] FAILED winbot / zope.security_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073141.html [12] FAILED winbot / ztk_10 py_254_win32 https://mail.zope.org/pipermail/zope-tests/2013-March/073144.html

1 0

Re: [Zope-dev] zope.security with Py3
by Tres Seaver 08 Mar '13

08 Mar '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/12/2013 10:47 PM, Stephan Richter wrote: > I saw you finished test coverage tonight for zope.security. What is > your timeline to do the port to Python 3? Our efforts are blocked > until we get zope.security going. We would be willing to take a shot > at the port, but you have just done all the hard work writing the > tests, so I do not want to steal the momentum from you. Now that the test coverage is in place, I plan to finish the Py3k conversion today, or tomorrow at the latest. 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/ iEYEARECAAYFAlEbuYMACgkQ+gerLs4ltQ4s3wCbBYky/rRSkkTnQPfkq6IJqwpq OQIAniAIFP3aBX/grlHM7wFcSYzknfCg =l8QV -----END PGP SIGNATURE-----

2 5

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

08 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-06 00:00:00 UTC and 2013-03-07 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 # 194 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.form_py_265_32 [5] winbot / z3c.formui_py_265_32 [6] winbot / z3c.layer.ready2go_py_265_32 [7] winbot / z3c.pagelet_py_265_32 [8] winbot / zope.app.authentication_py_265_32 [9] winbot / zope.app.authentication_py_265_32 [10] winbot / zope.app.http_py_265_32 [11] winbot / zope.app.pagetemplate_py_265_32 [12] winbot / zope.app.publication_py_265_32 [13] winbot / zope.app.publication_py_265_32 [14] winbot / zope.app.renderer_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 # 194 https://mail.zope.org/pipermail/zope-tests/2013-March/073119.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073117.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073135.html [4] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073112.html [5] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073115.html [6] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073113.html [7] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073114.html [8] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073134.html [9] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073111.html [10] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073132.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073118.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073133.html [13] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073110.html [14] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073116.html

3 2

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

07 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-05 00:00:00 UTC and 2013-03-06 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 # 193 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.formui_py_265_32 [4] winbot / z3c.language.switch_py_265_32 [5] winbot / z3c.layer.ready2go_py_265_32 [6] winbot / z3c.pagelet_py_265_32 [7] winbot / zc.resourcelibrary_py_265_32 [8] winbot / zope.app.http_py_265_32 [9] winbot / zope.app.pagetemplate_py_265_32 [10] winbot / zope.app.renderer_py_265_32 [11] winbot / zope.browserpage_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 # 193 https://mail.zope.org/pipermail/zope-tests/2013-March/073094.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073091.html [3] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073090.html [4] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073092.html [5] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073087.html [6] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073088.html [7] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073108.html [8] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073107.html [9] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073093.html [10] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073089.html [11] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073109.html

6 10

FYI2: Output Checker
by Stephan Richter 06 Mar '13

06 Mar '13

Hi everyone, when we ported TAL to Python 3, we had to fix the attribute order and I think Marius sorted them alphabetically. This would break a lot of existing tests. Luckily lxml provides and output checker that verifies the XML structure rather than the string representation. This will solve your HTML/XML output comparison issues. But often you also need your standard RE normalizers as well, but the 2 do not mix. For z3c.form I had developed an output checker that does both. I just released it as a separate package: https://pypi.python.org/pypi/zope.outputchecker Happy porting. :-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

1 0

FYI: random2
by Stephan Richter 06 Mar '13

06 Mar '13

Hi everyone, one of the issues while porting apps to Python 3 is that Python 3 uses a new algorithm for randrange(), which produces different output for Python 2 and 3. I just released random2, which is a port of Python 2.7's `random` module to Python 2.6, 3.2 and 3.3. This way your random output will not change while porting. Note: This is of course most useful to the ones among you that use sampledata generation heavily. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

1 0

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

06 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-04 00:00:00 UTC and 2013-03-05 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 # 192 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.form_py_265_32 [5] winbot / z3c.formui_py_265_32 [6] winbot / z3c.language.switch_py_265_32 [7] winbot / z3c.layer.ready2go_py_265_32 [8] winbot / z3c.menu.ready2go_py_265_32 [9] winbot / z3c.pagelet_py_265_32 [10] winbot / zc.resourcelibrary_py_265_32 [11] winbot / zope.app.authentication_py_265_32 [12] winbot / zope.app.http_py_265_32 [13] winbot / zope.app.pagetemplate_py_265_32 [14] winbot / zope.app.publication_py_265_32 [15] winbot / zope.app.renderer_py_265_32 [16] winbot / zope.browserpage_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 # 192 https://mail.zope.org/pipermail/zope-tests/2013-March/073068.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073066.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073086.html [4] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073062.html [5] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073065.html [6] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073067.html [7] FAILED winbot / z3c.layer.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073059.html [8] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073063.html [9] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073060.html [10] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073082.html [11] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073085.html [12] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073081.html [13] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073064.html [14] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073084.html [15] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073061.html [16] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073083.html

2 4