Re: [Zope-dev] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/22/2013 10:47 AM, Sebastien Douche wrote: > On Mon, Dec 3, 2012 at 10:44 AM, Sebastien Douche > wrote: >> Hi all, Does anyone (Tres?) can list ZTK packages w/o Python 3 >> support? > > What is the right version of ZODB : > > https://pypi.python.org/pypi/ZODB/4.0.0a4 or > https://pypi.python.org/pypi/ZODB3/3.11.0a2 ZODB 3.11.x will never be Py3k-compatible. ZODB 4.0.0a4 is not (yet) Py3k-compatible, but a 4.0.0 final release may be. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlEnxXsACgkQ+gerLs4ltQ6AFgCeP6OVEbewypKv3ThyXKx3YaqW C64AoLlDLp57SWDlEEUIoXa9u9pQGbdZ =rOZR -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 Mon, Dec 3, 2012 at 10:44 AM, Sebastien Douche wrote: > Hi all, > Does anyone (Tres?) can list ZTK packages w/o Python 3 support? What is the right version of ZODB : https://pypi.python.org/pypi/ZODB/4.0.0a4 or https://pypi.python.org/pypi/ZODB3/3.11.0a2 Some packages use the first, other the latter. -- Sebastien Douche 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 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 Design"http://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 )
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 Design"http://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
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
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
-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 > 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 Design"http://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 5:28 PM, Tres Seaver 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 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/19/2012 01:57 PM, Marius Gedminas wrote: > On Wed, Dec 19, 2012 at 01:37:04PM -0500, Tres Seaver wrote: >> On 12/19/2012 01:34 PM, Marius Gedminas wrote: >>> On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote: On 12/19/2012 11:33 AM, Tres Seaver wrote: > I spoke in error: the zope.proxy extension is ported. > However, there is a chunk of 'proxy.h' which is *not* compiled > when building the extension itself: it is only compiled when > included in another moduule. That bit needs porting: I will > push it out this wee. zope.proxy 4.1.0 released with that section Py3k compatible. Note that the cleanup required (enabling PyCapsule on Python 2.7) requires that extensions built under Python 2.7 against a 4.0.x version of the zope.proxy header must be rebuilt. >>> >>> What happens if they're not? Segfault? >> >> I think a little more graceful than that: you get a "module >> initialization error", or something. > > 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. > 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. Maybe a 3.9.0 release, made by branching from 3.8.3 and just bumping the zope.proxy dependency? Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDSGKsACgkQ+gerLs4ltQ73CwCfQQmFw/rKv4LQ9c3WwbPZT2oj iocAoJSEJonVZfDm+AuEN+Pj48F2MidH =tANQ -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 01:37:04PM -0500, Tres Seaver wrote: > On 12/19/2012 01:34 PM, Marius Gedminas wrote: > > On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote: > >> On 12/19/2012 11:33 AM, Tres Seaver wrote: > >>> I spoke in error: the zope.proxy extension is ported. However, > >>> there is a chunk of 'proxy.h' which is *not* compiled when > >>> building the extension itself: it is only compiled when included > >>> in another moduule. That bit needs porting: I will push it out > >>> this wee. > >> > >> zope.proxy 4.1.0 released with that section Py3k compatible. Note > >> that the cleanup required (enabling PyCapsule on Python 2.7) > >> requires that extensions built under Python 2.7 against a 4.0.x > >> version of the zope.proxy header must be rebuilt. > > > > What happens if they're not? Segfault? > > I think a little more graceful than that: you get a "module > initialization error", or something. 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? 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. 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 )
Re: [Zope-dev] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/2012 01:34 PM, Marius Gedminas wrote: > On Wed, Dec 19, 2012 at 01:07:10PM -0500, Tres Seaver wrote: >> On 12/19/2012 11:33 AM, Tres Seaver wrote: >>> I spoke in error: the zope.proxy extension is ported. However, >>> there is a chunk of 'proxy.h' which is *not* compiled when >>> building the extension itself: it is only compiled when included >>> in another moduule. That bit needs porting: I will push it out >>> this wee. >> >> zope.proxy 4.1.0 released with that section Py3k compatible. Note >> that the cleanup required (enabling PyCapsule on Python 2.7) >> requires that extensions built under Python 2.7 against a 4.0.x >> version of the zope.proxy header must be rebuilt. > > What happens if they're not? Segfault? I think a little more graceful than that: you get a "module initialization error", or something. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDSCVAACgkQ+gerLs4ltQ4U+ACfbz954FsE0jf5wfVtlVQ+zqbK pgUAn1hXqxIbkrqVTK9+jDIwF2g/z2/2 =cK6Z -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 01:07:10PM -0500, Tres Seaver wrote: > On 12/19/2012 11:33 AM, Tres Seaver wrote: > > I spoke in error: the zope.proxy extension is ported. However, there > > is a chunk of 'proxy.h' which is *not* compiled when building the > > extension itself: it is only compiled when included in another > > moduule. That bit needs porting: I will push it out this wee. > > zope.proxy 4.1.0 released with that section Py3k compatible. Note that > the cleanup required (enabling PyCapsule on Python 2.7) requires that > extensions built under Python 2.7 against a 4.0.x version of the > zope.proxy header must be rebuilt. What happens if they're not? Segfault? 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 )
Re: [Zope-dev] Current state of Python 3 migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/19/2012 11:33 AM, Tres Seaver wrote: > I spoke in error: the zope.proxy extension is ported. However, there > is a chunk of 'proxy.h' which is *not* compiled when building the > extension itself: it is only compiled when included in another > moduule. That bit needs porting: I will push it out this wee. zope.proxy 4.1.0 released with that section Py3k compatible. Note that the cleanup required (enabling PyCapsule on Python 2.7) requires that extensions built under Python 2.7 against a 4.0.x version of the zope.proxy header must be rebuilt. I updated the zope.security trunk to require zope.proxy >= 4.1.0. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDSAk0ACgkQ+gerLs4ltQ5wnQCgp/gQOhK9lDwZpD1CdGXimamG CfYAoMnVTGVwo7ja3nZebf8E3AuOimLY =rxpx -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/19/2012 11:28 AM, Tres Seaver wrote: > On 12/19/2012 09:53 AM, Sebastien Douche wrote: >> On Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche >> wrote: >>> I worked a bit this weekend on the buildbot for Python 3.3: > >> Another small step: Develop: >> '/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.security' > >> include/zope.proxy/proxy.h:36:17: warning: implicit declaration of >> function 'PyCObject_Check' [-Wimplicit-function-declaration] >> include/zope.proxy/proxy.h:38:25: warning: implicit declaration of >> function 'PyCObject_AsVoidPtr' [-Wimplicit-function-declaration] >> (... many warnings) src/zope/security/_proxy.c:993:20: error: >> 'PyTypeObject' has no member named 'ob_type' >> src/zope/security/_proxy.c:995:31: error: '_PyObject_GC_Del' >> undeclared (first use in this function) (... many warnings) > >> Tried with an official Ubuntu package and from source: same result. >> Missed something? > > 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. I spoke in error: the zope.proxy extension is ported. However, there is a chunk of 'proxy.h' which is *not* compiled when building the extension itself: it is only compiled when included in another moduule. That bit needs porting: I will push it out this wee. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDR7HYACgkQ+gerLs4ltQ7ODgCgsBHv604C7VnDiZFnESMrEhxJ b/kAoJ8/JrhRaeHydg1Le3u9QyX2XuE7 =tc1C -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/19/2012 09:53 AM, Sebastien Douche wrote: > On Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche > wrote: >> I worked a bit this weekend on the buildbot for Python 3.3: > > Another small step: Develop: > '/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.security' > > include/zope.proxy/proxy.h:36:17: warning: implicit declaration of > function 'PyCObject_Check' [-Wimplicit-function-declaration] > include/zope.proxy/proxy.h:38:25: warning: implicit declaration of > function 'PyCObject_AsVoidPtr' [-Wimplicit-function-declaration] (... > many warnings) src/zope/security/_proxy.c:993:20: error: > 'PyTypeObject' has no member named 'ob_type' > src/zope/security/_proxy.c:995:31: error: '_PyObject_GC_Del' > undeclared (first use in this function) (... many warnings) > > Tried with an official Ubuntu package and from source: same result. > Missed something? 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. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlDR60EACgkQ+gerLs4ltQ5K3QCfZWjS4m6v98ygJL0igh0UVZrE uqMAn1d4xpbE9zrCl5LKVjLqNabCis8z =D395 -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 Mon, Dec 17, 2012 at 2:45 PM, Sebastien Douche wrote: > I worked a bit this weekend on the buildbot for Python 3.3: Another small step: Develop: '/home/sdouche/bb/slave/ztk1.1dev/Python3.3.0-Linux-64bit/build/src/zope.security' include/zope.proxy/proxy.h:36:17: warning: implicit declaration of function 'PyCObject_Check' [-Wimplicit-function-declaration] include/zope.proxy/proxy.h:38:25: warning: implicit declaration of function 'PyCObject_AsVoidPtr' [-Wimplicit-function-declaration] (... many warnings) src/zope/security/_proxy.c:993:20: error: 'PyTypeObject' has no member named 'ob_type' src/zope/security/_proxy.c:995:31: error: '_PyObject_GC_Del' undeclared (first use in this function) (... many warnings) Tried with an official Ubuntu package and from source: same result. Missed something? The log: http://buildbot.afpy.org/ztk1.1dev/builders/Python3.3.0%20Linux%2064bit/builds/6/steps/buildout/logs/stdio -- Sebastien Douche 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
On Mon, Dec 17, 2012 at 2:49 PM, Adam GROSZER wrote: >> - bootstrap.py seems too old. >> > > winbot uses there *one* central bootstrap.py for all packages > > e.g. see: > http://winbot.zope.org/builders/zope.browserresource_py_265_32/builds/704/steps/bootstrap/logs/stdio Done, thanks Adam. -- Sebastien Douche 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
On 12/17/2012 02:45 PM, Sebastien Douche wrote: On Mon, Dec 3, 2012 at 4:14 PM, Sebastien Douche wrote: Thanks Tres, I will try in the first step to add a Python 3.3 Buildbot for all ZTK packages (+ most important ZopApp packages). I worked a bit this weekend on the buildbot for Python 3.3: - bootstrap.py seems too old. winbot uses there *one* central bootstrap.py for all packages e.g. see: http://winbot.zope.org/builders/zope.browserresource_py_265_32/builds/704/steps/bootstrap/logs/stdio -- Best regards, Adam GROSZER -- Quote of the day: To have more, desire less. - Table Talk ___ 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 Mon, Dec 3, 2012 at 4:14 PM, Sebastien Douche wrote: > Thanks Tres, I will try in the first step to add a Python 3.3 Buildbot > for all ZTK packages (+ most important ZopApp packages). I worked a bit this weekend on the buildbot for Python 3.3: - bootstrap.py seems too old. - Some packages aren't compatible with Python 3.3 (must pin them): mr.developer = 1.23 zc.buildout = 2.0.0a5 zc.recipe.egg = 2.0.0a3 - z3c.recipe.compattest is not compatible with Python 3.3 and newer versions of zc.recipe.egg (it use _BackwardsSupportOption) -- Sebastien Douche 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
On Mon, Dec 3, 2012 at 2:57 PM, Tres Seaver wrote: > My current porting focus is on the ZODB-related packages, which are the > last ones needed for a typical Zope-like Pyramid application. I would be > glad to help anybody who would like to tackle other ZTK packages figure > out the pattern (use tox, get to 100% coverage, then convert to a > "straddle" / "compatible subset" dialect). Thanks Tres, I will try in the first step to add a Python 3.3 Buildbot for all ZTK packages (+ most important ZopApp packages). -- Sebastien Douche 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/03/2012 04:44 AM, Sebastien Douche wrote: > Does anyone (Tres?) can list ZTK packages w/o Python 3 support? These pacckages support Python 3.2 and 3.3, as well as current PyPy, and are tested do do so via jenkins / tox[1]: - - zope.component - - zope.configuration - - zope.deprecation - - zope.event - - zope.exceptions - - zope.i18nmessageid - - zope.interface - - zope.schema These packages support Python 3.2 and 3.3 and PyPy, but are not being regularly tested on those versions by that Jenkins / tox setup: - - zope.copy - - zope.hookable - - zope.location - - zope.proxy - - zope.testing This package says it supports Python 3.1. It is not being tested - - zope.testrunner [1] http://jenkins.pylonsproject.org/ My current porting focus is on the ZODB-related packages, which are the last ones needed for a typical Zope-like Pyramid application. I would be glad to help anybody who would like to tackle other ZTK packages figure out the pattern (use tox, get to 100% coverage, then convert to a "straddle" / "compatible subset" dialect). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlC8r8QACgkQ+gerLs4ltQ4yTwCfSqRNrCU612EZIlkO0WiK8gPm FmUAoJ0E6yuvVoIochZjwSq0nqId1YX3 =X8HA -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] Current state of Python 3 migration
Hi all, Does anyone (Tres?) can list ZTK packages w/o Python 3 support? -- Sebastien Douche 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 )
