Re: [Zope-dev] zope.security with Py3
On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:15 PM, Tres Seaver wrote: The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. I put that work on a branch: https://github.com/zopefoundation/zope.security/tree/pure_python_proxy Likely I won't get back to it this week. Hi Tres, do you see yourself working on this again soon? I was going to port some packages to PyPy, but got quickly blocked by zope.security. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ 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.security with Py3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/08/2013 02:18 PM, Stephan Richter wrote: On Thursday, February 14, 2013 03:42:06 PM Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/14/2013 03:15 PM, Tres Seaver wrote: The work to create a compatible pure-Python proxy is partly done (I added tests for all the features of the C version I could discover). The version I have in my sandbox doesn't pass all those tests, so I haven't pushed it. I put that work on a branch: https://github.com/zopefoundation/zope.security/tree/pure_python_proxy Likely I won't get back to it this week. Hi Tres, do you see yourself working on this again soon? I was going to port some packages to PyPy, but got quickly blocked by zope.security. No, I don't think I will be working on that package in the near future (I pushed changes merging the trunk and fixed the coverage today). 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/ iEYEARECAAYFAlE6S1AACgkQ+gerLs4ltQ75/ACbBoPUgnPVEFPBLorH5SRiYnXX vfIAmgKOsillJ0VLZzZsxsQ2L48z48PI =C34r -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 )
[Zope-dev] zope-tests - FAILED: 12, OK: 11
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 ___ 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 )
