Re: [Zope-dev] Current state of Python 3 migration
On Wed, Dec 19, 2012 at 5:28 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/2012 09:53 AM, Sebastien Douche wrote: zope.proxy's C extension is not yet ported to Py3k. Having just wrestled through the persisetnt and BTrees extensions, I might be able to port it fairly quickly. Next step, zope.hookable :). Develop: '/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.hookable' src/zope/hookable/_zope_hookable.c: In function 'hookable_dealloc': src/zope/hookable/_zope_hookable.c:83:7: error: 'hookable' has no member named 'ob_type' src/zope/hookable/_zope_hookable.c: At top level: src/zope/hookable/_zope_hookable.c:138:55: error: 'RO' undeclared here (not in a function) (many warnings) src/zope/hookable/_zope_hookable.c:159:27: error: 'cmpfunc' undeclared here (not in a function) src/zope/hookable/_zope_hookable.c:159:26: error: initializer element is not constant src/zope/hookable/_zope_hookable.c:159:26: error: (near initialization for 'hookabletype.tp_repr') src/zope/hookable/_zope_hookable.c:159:35: error: expected '}' before numeric constant src/zope/hookable/_zope_hookable.c: In function 'init_zope_hookable': src/zope/hookable/_zope_hookable.c:208:26: error: '_PyObject_GC_Del' undeclared (first use in this function) (many warnings) The log: http://buildbot.afpy.org/ztk1.1dev/builders/Python3.3.0%20Linux%2064bit/builds/7/steps/buildout/logs/stdio -- Sebastien Douche sdou...@gmail.com Twitter: @sdouche / G+: +sdouche ___ 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] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/20/2012 04:49 AM, Sebastien Douche wrote: On Wed, Dec 19, 2012 at 5:28 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/2012 09:53 AM, Sebastien Douche wrote: zope.proxy's C extension is not yet ported to Py3k. Having just wrestled through the persisetnt and BTrees extensions, I might be able to port it fairly quickly. Next step, zope.hookable :). Develop: '/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.hookable' src/zope/hookable/_zope_hookable.c: In function 'hookable_dealloc': src/zope/hookable/_zope_hookable.c:83:7: error: 'hookable' has no member named 'ob_type' src/zope/hookable/_zope_hookable.c: At top level: src/zope/hookable/_zope_hookable.c:138:55: error: 'RO' undeclared here (not in a function) (many warnings) src/zope/hookable/_zope_hookable.c:159:27: error: 'cmpfunc' undeclared here (not in a function) src/zope/hookable/_zope_hookable.c:159:26: error: initializer element is not constant src/zope/hookable/_zope_hookable.c:159:26: error: (near initialization for 'hookabletype.tp_repr') src/zope/hookable/_zope_hookable.c:159:35: error: expected '}' before numeric constant src/zope/hookable/_zope_hookable.c: In function 'init_zope_hookable': src/zope/hookable/_zope_hookable.c:208:26: error: '_PyObject_GC_Del' undeclared (first use in this function) (many warnings) That is not the trunk version of zope.hookable, but the one on the 3.4 branch (never gonna be Py3k compatible). 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/ iEYEARECAAYFAlDTGUsACgkQ+gerLs4ltQ5+MQCfayCLoaDrky/lF/ljlkAMfC4j Pd4AoIftYHstYW8tkQQWFNXutohsyI6V =jx8I -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] Current state of Python 3 migration
On Wed, Dec 19, 2012 at 02:42:35PM -0500, Tres Seaver wrote: On 12/19/2012 01:57 PM, Marius Gedminas wrote: Yeah, just got this SystemError: dynamic module not initialized properly when I checked out z3c.ptcompat, bootstrapped, buildouted, and ran bin/test. This is a bit unpleasant: I've zope.security 3.8.3 in my shared buildout eggs directory. If I wipe it and reinstall, I'll get it built ABI-compatible with zope.proxy 4.1.0 and all my existing buildouts that used zope.security 3.8.3 with an older zope.proxy will stop working. If I don't wipe it, I can't create any new buildouts that pull in an unversioned dependency on zope.proxy. Ideas? Ugh, that hurts. I don't ever use the shared directory, so I missed that possibility. (It's a wonderful time-saver, and I would even call it a killer feature for zc.buildout.) Would it be possible to release zope.security 4.0.0 any time soonish? Then new buildouts would get new zope.proxy and new zope.security, while old buildouts would happily continue to use old ones. I had hoped that the 4.0.0 marker would signal Py3k compatibilty, but don't have gumption to finish that port today. Whoops. I think I accidentally stepped on your toes by releasing zope.pagetemplate 4.0.0 without first checking if the Py3k port was complete. I just assumed it was, after noticing the 4.0.0 version number in CHANGES.txt. Maybe a 3.9.0 release, made by branching from 3.8.3 and just bumping the zope.proxy dependency? That sounds reasonable. Marius Gedminas -- I heard the story of an assembly programmer who put several ret instructions at the end of a subroutine... and more, for longer subroutines, because of momentum. -- 9ren on reddit 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 )
Re: [Zope-dev] Current state of Python 3 migration
On Thu, Dec 20, 2012 at 05:13:37PM +0200, Marius Gedminas wrote: On Wed, Dec 19, 2012 at 02:42:35PM -0500, Tres Seaver wrote: On 12/19/2012 01:57 PM, Marius Gedminas wrote: Would it be possible to release zope.security 4.0.0 any time soonish? Then new buildouts would get new zope.proxy and new zope.security, while old buildouts would happily continue to use old ones. I had hoped that the 4.0.0 marker would signal Py3k compatibilty, but don't have gumption to finish that port today. Whoops. I think I accidentally stepped on your toes by releasing zope.pagetemplate 4.0.0 without first checking if the Py3k port was complete. I just assumed it was, after noticing the 4.0.0 version number in CHANGES.txt. I added a tox.ini and 'setup.py test' support to zope.pagetemplate trunk and saw that Py3k porting is blocked by zope.security not working with Py3k yet. No pressure ;-) Maybe a 3.9.0 release, made by branching from 3.8.3 and just bumping the zope.proxy dependency? That sounds reasonable. Call that a +0.5 vote, because I don't trust my judgment. Marius Gedminas -- Software programmers should not think that they have to write multi-threaded programs. It's too hard, and the payoff is too little. And it absolutely isn't where the industry is even going. -- Linus Torvalds 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 )
Re: [Zope-dev] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/20/2012 10:21 AM, Marius Gedminas wrote: On Thu, Dec 20, 2012 at 05:13:37PM +0200, Marius Gedminas wrote: On Wed, Dec 19, 2012 at 02:42:35PM -0500, Tres Seaver wrote: On 12/19/2012 01:57 PM, Marius Gedminas wrote: Would it be possible to release zope.security 4.0.0 any time soonish? Then new buildouts would get new zope.proxy and new zope.security, while old buildouts would happily continue to use old ones. I had hoped that the 4.0.0 marker would signal Py3k compatibilty, but don't have gumption to finish that port today. Whoops. I think I accidentally stepped on your toes by releasing zope.pagetemplate 4.0.0 without first checking if the Py3k port was complete. I just assumed it was, after noticing the 4.0.0 version number in CHANGES.txt. I added a tox.ini and 'setup.py test' support to zope.pagetemplate trunk and saw that Py3k porting is blocked by zope.security not working with Py3k yet. No pressure ;-) Maybe a 3.9.0 release, made by branching from 3.8.3 and just bumping the zope.proxy dependency? That sounds reasonable. Call that a +0.5 vote, because I don't trust my judgment. I'm actually thinking tat a 3.8.4 release (only tightening the zope.proxy requirement) would be even better: there are no new features, nor BBB issues for consumers of zope.security, as a 3.9.0 release might signal. I will push it out shortly. 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/ iEYEARECAAYFAlDTb10ACgkQ+gerLs4ltQ6MiACgi17brooklRlmhtl1+8oB+BTz 8JQAoITmWcKq98vISePvuHMgi56C9BiC =PF/n -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] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/20/2012 03:04 PM, Tres Seaver wrote: I'm actually thinking tat a 3.8.4 release (only tightening the zope.proxy requirement) would be even better: there are no new features, nor BBB issues for consumers of zope.security, as a 3.9.0 release might signal. I will push it out shortly. Done. 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/ iEYEARECAAYFAlDTcI4ACgkQ+gerLs4ltQ4bjgCgli8DGjwel+B4lIbgzgBGxejr YlkAoNsePK5GjktmoxG/02Xv48bB3NT1 =lkH6 -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: 48, OK: 19
This is the summary for test reports received on the zope-tests list between 2012-12-19 00:00:00 UTC and 2012-12-20 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]Failure - zopetoolkit_trunk - Build # 112 [2]Failure - zopetoolkit_trunk_app - Build # 96 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 [3]winbot / BTrees_py_265_32 winbot / ZODB_dev py_265_win32 winbot / ZODB_dev py_265_win64 winbot / ZODB_dev py_270_win32 winbot / ZODB_dev py_270_win64 [4]winbot / z3c.baseregistry_py_265_32 [5]winbot / z3c.form_py_265_32 [6]winbot / z3c.formui_py_265_32 [7]winbot / z3c.json_py_265_32 [8]winbot / z3c.language.negotiator_py_265_32 [9]winbot / z3c.macro_py_265_32 [10] winbot / z3c.menu.ready2go_py_265_32 [11] winbot / z3c.pdftemplate_py_265_32 [12] winbot / z3c.ptcompat_py_265_32 [13] winbot / z3c.recipe.paster_py_265_32 [14] winbot / z3c.template_py_265_32 [15] winbot / z3c.testing_py_265_32 [16] winbot / z3c.xmlhttp_py_265_32 [17] winbot / zc.catalog_py_265_32 [18] winbot / zc.sourcefactory_py_265_32 [19] winbot / zc.table_py_265_32 [20] winbot / zope.app.applicationcontrol_py_265_32 [21] winbot / zope.app.authentication_py_265_32 [22] winbot / zope.app.broken_py_265_32 [23] winbot / zope.app.component_py_265_32 [24] winbot / zope.app.debug_py_265_32 [25] winbot / zope.app.error_py_265_32 [26] winbot / zope.app.form_py_265_32 [27] winbot / zope.app.generations_py_265_32 [28] winbot / zope.app.http_py_265_32 [29] winbot / zope.app.pagetemplate_py_265_32 [30] winbot / zope.app.renderer_py_265_32 [31] winbot / zope.app.rotterdam_py_265_32 [32] winbot / zope.app.schema_py_265_32 [33] winbot / zope.app.server_py_265_32 [34] winbot / zope.app.session_py_265_32 [35] winbot / zope.app.testing_py_265_32 [36] winbot / zope.app.zopeappgenerations_py_265_32 [37] winbot / zope.applicationcontrol_py_265_32 [38] winbot / zope.browsermenu_py_265_32 [39] winbot / zope.catalog_py_265_32 [40] winbot / zope.component_py_265_32 [41] winbot / zope.contentprovider_py_265_32 [42] winbot / zope.formlib_py_265_32 [43] winbot / zope.generations_py_265_32 [44] winbot / zope.lifecycleevent_py_265_32 [45] winbot / zope.login_py_265_32 [46] winbot / zope.pluggableauth_py_265_32 [47] winbot / zope.publisher_py_265_32 [48] winbot / zope.traversing_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 Failure - zopetoolkit_trunk - Build # 112 https://mail.zope.org/pipermail/zope-tests/2012-December/070348.html [2]FAILED Failure - zopetoolkit_trunk_app - Build # 96 https://mail.zope.org/pipermail/zope-tests/2012-December/070349.html [3]FAILED winbot / BTrees_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070373.html [4]FAILED winbot / z3c.baseregistry_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070404.html [5]FAILED winbot / z3c.form_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070393.html [6]FAILED winbot / z3c.formui_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070381.html [7]FAILED winbot / z3c.json_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070392.html [8]FAILED winbot / z3c.language.negotiator_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070385.html [9]FAILED winbot / z3c.macro_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070408.html [10] FAILED winbot / z3c.menu.ready2go_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070403.html [11] FAILED winbot / z3c.pdftemplate_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070407.html [12] FAILED winbot / z3c.ptcompat_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070346.html [13] FAILED winbot / z3c.recipe.paster_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070347.html [14] FAILED winbot / z3c.template_py_265_32 https://mail.zope.org/pipermail/zope-tests/2012-December/070411.html [15] FAILED winbot /
