The porting howto.

[Lennart Regebro]

I just read Bretts new porting howto, and it's good, except for one
omission. The strategies section makes it sound like you can't use
2to3 to support both Python 2 and Python 3, while it in fact can be
easily supported by running 2to3 on build time with distutils or even
better Distribute. This should be mentioned, IMO.

Feel free to take parts of my Strategies chapter:
http://python3porting.com/strategies.html

//Lennart

[Brett Cannon]

I'll fix the omission.

Post by Lennart Regebro
I just read Bretts new porting howto, and it's good, except for one
omission. The strategies section makes it sound like you can't use
2to3 to support both Python 2 and Python 3, while it in fact can be
easily supported by running 2to3 on build time with distutils or even
better Distribute. This should be mentioned, IMO.
http://python3porting.com/strategies.html
//Lennart
_______________________________________________
Python-porting mailing list
http://mail.python.org/mailman/listinfo/python-porting

[Brett Cannon]

I had a chance to look at this and I see what you mean about the intro
being a little heavy-handed against 2to3. I have simplified it and
left the more thorough discussion in the various sectional discussions
cover the details.

I will see if Georg will let me slip this into Python 3.2.0.

Post by Lennart Regebro
I just read Bretts new porting howto, and it's good, except for one
omission. The strategies section makes it sound like you can't use
2to3 to support both Python 2 and Python 3, while it in fact can be
easily supported by running 2to3 on build time with distutils or even
better Distribute. This should be mentioned, IMO.
http://python3porting.com/strategies.html
//Lennart
_______________________________________________
Python-porting mailing list
http://mail.python.org/mailman/listinfo/python-porting