On Tue, 19 Jun 2012 08:55:51 -0700
Glyph <gl...@twistedmatrix.com> wrote:
>
> On Jun 19, 2012, at 7:43 AM, Vladimir Perić wrote:
>
> > there are basically two strategies:
> > maintaining py2 code and using 2to3 when installing under py3, or
> > maintaining a codebase which is compatible with both 2 and 3
>
> Based on the experiences of other porters I have talked to, and heard
> speaking on mailing lists, 2to3 still has yet to live up to its promise, and
> a unified codebase is much more manageable. That said, there are syntax
> changes ('except...as...' being the big one) that make supporting 2.5->3
> difficult, and only becomes reasonable at 2.6->3.
A shared codebase definitely isn't reasonable if you want to support
Python 2.5. At least not for a project the size of Twisted.
(why doesn't your mail / news client word wrap paragraps?)
Regards
Antoine.
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
