Re: [Zope-dev] Python 3 support status page
On Mon, Jan 28, 2013 at 10:41:59PM +0100, Lennart Regebro wrote: On Mon, Jan 28, 2013 at 6:27 PM, Marius Gedminas mar...@gedmin.as wrote: I wanted to have an up-to-date status page for the status of the Python 3 porting efforts of various zope-ish packages, so I made one: http://zope3.pov.lt/py3/ Awesome. But do we have to call it Zope3? :-) What should I call it, BlueBream? ZTK? Just Zope? Hmm, Zope, in the sense of all packages maintained under the aegis of the Zope Foundation, seems reasonable, as long as people won't assume the page was about Zope2. The Pyramid folks have a Pylons Project, which will develop a collection of related technologies [r]ather than focusing on a single web framework. Sounds familiar. Should there be a Zope Project, to encompass Zope 2, Zope 3/BlueBream, ZTK, Grok, and everything else? In other news, experts discuss the best color for bike sheds. Stay tuned. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development signature.asc Description: Digital signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope-tests - FAILED: 2, OK: 20
This is the summary for test reports received on the zope-tests list between 2013-01-28 00:00:00 UTC and 2013-01-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 Successful - zopetoolkit_trunk - Build # 155 Successful - zopetoolkit_trunk_app - Build # 138 Zope-2.10 Python-2.4.6 : Linux Zope-2.11 Python-2.4.6 : Linux Zope-2.12 Python-2.6.8 : Linux Zope-2.13 Python-2.6.8 : Linux Zope-2.13 Python-2.7.3 : Linux Zope-trunk Python-2.6.8 : Linux Zope-trunk Python-2.7.3 : Linux winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 [1]winbot / ZODB_dev py_270_win64 [2]winbot / z3c.recipe.paster_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 winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071764.html [2]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071765.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope-tests - FAILED: 2, OK: 20
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/29/2013 08:00 PM, Zope tests summarizer wrote: [1]FAILED winbot / ZODB_dev py_270_win64 https://mail.zope.org/pipermail/zope-tests/2013-January/071764.html I'm not terribly certain, but this looks like a timeout / race condition on a test, perhaps due to load on the machine? Failure in test c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt -- File c:\buildslave\zodb_dev_py_270_win64\build\src\ZODB\historical_connections.txt, line 220, in historical_connections.txt Failed example: [c in conns1 for c in conns2] Expected: [False, False, True, True] Got: [False, False, False, True] The text above the failed example seems to expect that the first two connections would have timed out / been garbage collected, but that the second two would be fresh enough to be reused. [2]FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2013-January/071765.html The same failure. I reiterate that somebody who knows / cares about the 'zc.recipe.paster' project needs to step in an fix this failure, or else we need to retire its nightly test run. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlEIftQACgkQ+gerLs4ltQ5scgCdESe9ZLgWyKZwYPVxxKzvnPcN diMAoKj/JEfukaFwUO9O9KzcsMo5go+T =9qq4 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Python 3 support status page
On Tue, Jan 29, 2013 at 1:59 PM, Marius Gedminas mar...@gedmin.as wrote: On Mon, Jan 28, 2013 at 10:41:59PM +0100, Lennart Regebro wrote: On Mon, Jan 28, 2013 at 6:27 PM, Marius Gedminas mar...@gedmin.as wrote: I wanted to have an up-to-date status page for the status of the Python 3 porting efforts of various zope-ish packages, so I made one: http://zope3.pov.lt/py3/ Awesome. But do we have to call it Zope3? :-) What should I call it, BlueBream? ZTK? Just Zope? Hmm, Zope, in the sense of all packages maintained under the aegis of the Zope Foundation, seems reasonable, as long as people won't assume the page was about Zope2. The Pyramid folks have a Pylons Project, which will develop a collection of related technologies [r]ather than focusing on a single web framework. Sounds familiar. Should there be a Zope Project, to encompass Zope 2, Zope 3/BlueBream, ZTK, Grok, and everything else? In other news, experts discuss the best color for bike sheds. Stay tuned. Yeah, ZTK, Zope or Zope Project all work. //Lennart ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
