Re: [Zope-dev] Zope vs. Python 3 porting roadmap

2010-11-24 Thread Lennart Regebro
Oh, and zc.buildout also exposes bugs in Distribute under Python 3, so a new version of Distribute is needed before this can be finished. But that could probably happen quite fast after I get most of the zc.buildout tests running. ___ Zope-Dev maillist -

Re: [Zope-dev] Zope vs. Python 3 porting roadmap

2010-11-24 Thread Lennart Regebro
On Tue, Nov 23, 2010 at 22:21, Jim Fulton wrote: > This is like saying it needed to support Python 2 before it could be > written on Python 2. With the difference that it's written bit by bit, but needs to get ported all at once. Of course, if you know which tests to get to pass first it's easier

Re: [Zope-dev] Zope vs. Python 3 porting roadmap

2010-11-23 Thread Jim Fulton
On Tue, Nov 23, 2010 at 4:09 PM, Lennart Regebro wrote: > High hanging fruit: > === > zc.buildout: (depends on itself, hard to use 2to3) >    setuptools - Done >    zope.testing - [test] Done, not released > COMMENT: Since zc.buildout uses itself to install and run and test, it nee

[Zope-dev] Zope vs. Python 3 porting roadmap

2010-11-23 Thread Lennart Regebro
Hi all! Hanno asked me to write this up, so I did. Done and released: == setutools (ie distribute) zope.interface zope.event zope.exceptions Low hanging fruit: == zope.i18nmessageid: Done - not merged    setuptools - Done TODO: Test the regebro-python3 branch w