- Zope-Dev - Zope lists

Who has the winbot/rackspace creds?
by Adam GROSZER 05 Mar '13

05 Mar '13

Hello, It would be time to do a backup/snapshot of the VM. -- Best regards, Adam GROSZER -- Quote of the day: The man who smiles when things go wrong has thought of someone he can blame it on. - Jones' Law

1 0

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

05 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-03 00:00:00 UTC and 2013-03-04 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 # 191 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.language.switch_py_265_32 [6] winbot / z3c.menu.ready2go_py_265_32 [7] winbot / z3c.pagelet_py_265_32 [8] winbot / zc.resourcelibrary_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.renderer_py_265_32 [14] winbot / zope.browserpage_py_265_32 [15] winbot / zope.formlib_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 # 191 https://mail.zope.org/pipermail/zope-tests/2013-March/073041.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073039.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073034.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073038.html [5] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073040.html [6] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073035.html [7] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073032.html [8] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073058.html [9] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073056.html [10] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073057.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073036.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073055.html [13] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073033.html [14] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073054.html [15] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073037.html

2 1

ZTK 2.0: Deprecate zope.sequencesort
by Stephan Richter 04 Mar '13

04 Mar '13

Hi everyone, I would like to deprecate zope.sequencesort in ZTK 2.0, since it cannot properly ported to Python 3, since it depends heavily on the cmp() way of sorting. I am also not a user of the package and I only tried to port the package for completeness sake. Thoughts? Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

9 20

zope-tests - FAILED: 18, OK: 13
by Zope tests summarizer 04 Mar '13

04 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-02 00:00:00 UTC and 2013-03-03 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 436 projects [2] Still Failing - zopetoolkit_trunk - Build # 190 Total languishing bugs for zope2: 0 [3] Total languishing bugs for zope: 69 [4] Total languishing bugs for zopeapp: 1 [5] Total languishing bugs for zopetoolkit: 205 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.language.switch_py_265_32 [10] winbot / z3c.pagelet_py_265_32 [11] winbot / zc.resourcelibrary_py_265_32 [12] winbot / zope.app.authentication_py_265_32 [13] winbot / zope.app.http_py_265_32 [14] winbot / zope.app.pagetemplate_py_265_32 [15] winbot / zope.app.publication_py_265_32 [16] winbot / zope.app.renderer_py_265_32 [17] winbot / zope.browserpage_py_265_32 [18] winbot / zope.formlib_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 436 projects https://mail.zope.org/pipermail/zope-tests/2013-March/073014.html [2] FAILED Still Failing - zopetoolkit_trunk - Build # 190 https://mail.zope.org/pipermail/zope-tests/2013-March/073013.html [3] FAILED Total languishing bugs for zope: 69 https://mail.zope.org/pipermail/zope-tests/2013-March/073011.html [4] FAILED Total languishing bugs for zopeapp: 1 https://mail.zope.org/pipermail/zope-tests/2013-March/073009.html [5] FAILED Total languishing bugs for zopetoolkit: 205 https://mail.zope.org/pipermail/zope-tests/2013-March/073010.html [6] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073007.html [7] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073003.html [8] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073006.html [9] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073008.html [10] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073001.html [11] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073031.html [12] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073029.html [13] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073030.html [14] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073004.html [15] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073028.html [16] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073002.html [17] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073027.html [18] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073005.html

2 1

"procedures" for moving package to github and porting to Python 3
by Jan-Wijbrand Kolman 04 Mar '13

04 Mar '13

Hi, Disclaimer: it's been a while since I actively followed zope-dev and grok-dev. So, please forgive me my ignorance. Spurred by the recent ZTK-2.0 discussion, I'm trying to get back on track on the topics of 1) migrating package to github and 2) porting packages to Python 3. As a first step, I'd like to get the packages directly related to Grok moved over to github. Could someone perhaps tell me if there's a guideline document, some kind of recipe, or perhaps a "conclusive" posting on the mailinglist on how to proceed on this topic? Thanks in advance for any pointers!! kind regards, jw

4 13

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

04 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-03-01 00:00:00 UTC and 2013-03-02 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 # 189 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.language.switch_py_265_32 [6] winbot / z3c.layer.pagelet_py_265_32 [7] winbot / z3c.pagelet_py_265_32 [8] winbot / zc.resourcelibrary_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.renderer_py_265_32 [14] winbot / zope.browserpage_py_265_32 [15] winbot / zope.formlib_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 # 189 https://mail.zope.org/pipermail/zope-tests/2013-March/072982.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072979.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072975.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072978.html [5] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072981.html [6] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072996.html [7] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072974.html [8] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/073000.html [9] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072998.html [10] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072999.html [11] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072976.html [12] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072997.html [13] FAILED winbot / zope.app.renderer_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072980.html [14] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072995.html [15] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072977.html

5 4

SVN to Git Conversion
by Stephan Richter 04 Mar '13

04 Mar '13

Hi everyone, I am now feeling comfortable with my script to run conversions of many packages at once. Thus, if you want packages moved from SVN to GitHub just let me know and I will convert them for you. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

2 2

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

02 Mar '13

This is the summary for test reports received on the zope-tests list between 2013-02-28 00:00:00 UTC and 2013-03-01 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 # 188 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.language.switch_py_265_32 [6] winbot / z3c.layer.pagelet_py_265_32 [7] winbot / z3c.layer.pagelet_py_265_32 [8] winbot / z3c.pagelet_py_265_32 [9] winbot / z3c.recipe.paster_py_265_32 [10] winbot / zc.catalog_py_265_32 [11] winbot / zc.queue_py_265_32 [12] winbot / zc.resourcelibrary_py_265_32 [13] winbot / zope.app.authentication_py_265_32 [14] winbot / zope.app.http_py_265_32 [15] winbot / zope.app.pagetemplate_py_265_32 [16] winbot / zope.app.publication_py_265_32 [17] winbot / zope.browserpage_py_265_32 [18] winbot / zope.formlib_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 # 188 https://mail.zope.org/pipermail/zope-tests/2013-March/072952.html [2] FAILED winbot / z3c.contents_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072949.html [3] FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072945.html [4] FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072948.html [5] FAILED winbot / z3c.language.switch_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072951.html [6] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072968.html [7] FAILED winbot / z3c.layer.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072950.html [8] FAILED winbot / z3c.pagelet_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072944.html [9] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072965.html [10] FAILED winbot / zc.catalog_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072966.html [11] FAILED winbot / zc.queue_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072973.html [12] FAILED winbot / zc.resourcelibrary_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072972.html [13] FAILED winbot / zope.app.authentication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072970.html [14] FAILED winbot / zope.app.http_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072971.html [15] FAILED winbot / zope.app.pagetemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072946.html [16] FAILED winbot / zope.app.publication_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072969.html [17] FAILED winbot / zope.browserpage_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072967.html [18] FAILED winbot / zope.formlib_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-March/072947.html

2 1

Porting Zope to Python 3 Update
by Stephan Richter 02 Mar '13

02 Mar '13

Hi everyone, as the week ends, I thought I might give a brief update on the Python 3 porting effort. According to the "Unofficial Zope on Python 3 status page"[1], about 110 packages are ported to Python 3.3. Hanno and I worked this week on updating the ZTK configuration files and I am happy to announce that the ZTK passes all tests on Python 3.3! So once the ZODB is ported, we can start on finalizing all releases, which would pave the way for a ZTK 2.0 release. Marius has made great efforts on finishing the port of ZODB. All the tests pass now on the py3 branch for Python 2.6, 2.7 and 3.3. He has also removed all resource warnings (he started at 400+). The final task will be to integrate zodbpickle. zodbpickle needs some changes to properly enable the "noload()" method. Luckily this work will entail rewriting the dump/load of persistent ids to be more efficient and compatible with cPickle 2.7 pickles. (We are working hard on making Python 2 pickles load on Python 3!) On Wednesday, I was able to run a first Zope 3 (or should I say Bluebream?) app on Python 3.3. Thanks to Andrey and Albertas for porting some of the complex application packages. The sample application can be found in ``zope.paste``[2]. Note the short ZCML[3] and Paster[4] files. Thanks goes to everyone who helped breaking unnecessary and circular dependencies to make this work so well! In the process of all of the above, we have also started moving all packages that we are ported to Python 3 over to GitHub. I have also ported the core packages for Zope 2/4 and Grok already. So what's next? I am in the process of trying to port a rather large demo application[5] to Python 3. We are about 20 packages (that we control) away from that goal. Andrey is currently working on porting zope.testbrowser to Python 3 by changing its internal implementation from mechanize to WebTest (since it is too hard to deal with mechanize). Also, we will have a serious look at ZEO. I hope I got some of you interested in thinking about porting applications to Python 3. [1] http://zope3.pov.lt/py3/ [2] https://github.com/zopefoundation/zope.paste [3] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/tes… [4] https://github.com/zopefoundation/zope.paste/blob/master/src/zope/paste/tes… [5] https://github.com/CipherHealth/cipher.uibuilderdemo Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter"

2 1

Zope2 git mirror not updating?
by Wichert Akkerman 02 Mar '13

02 Mar '13

I noticed that the Zope2 git mirror does not appear to be updating. Looking at https://github.com/zopefoundation/Zope/commits/2.13 it doesn't have any commits after November 15, while subversion has more recent commits from Hanno and Maurits. Did an updating process break? Or did development switch to github but the subversion repository was not made readonly? Wichert.

3 3