I am proud to announce the third alpha release of 3to2: 0.1a3. Release notes can be found in the RELEASE file.
Note that the Python 3.1 branch requires patching lib2to3 to be able to run the unpacking fixer, which is disabled by default for this reason. If you have no problems patching lib2to3 in this way and wish to have the fixer enabled by default, you may manually edit lib3to2/fixes/fix_unpacking.py and delete the line that says “explicit = True” before running setup.py. (If you do this after running setup.py, then you will have to run it again.)
New to this version of 3to2 is a slightly enhanced Makefile. Users of UNIX-like machines can run “make install-local” to install 3to2 to $HOME/.local, “make test-local” to install 3to2 locally and run the test suite, and “make uninstall-local” to remove 3to2′s presence from $HOME/.local
Python 2.7: gzipped tarball is available at bitbucket, and there is also a mercurial branch of the source. 2.7 releases will be tagged versions of the trunk.
Python 3.1: gzipped tarball is available at bitbucket (if you downloaded this before 4:00 PM EDT today (Oct 28), please re-download. It has been updated. Thank bitbucket.), and there is also a mercurial branch of the source. 3.1 releases will be discreet, as 2to3 is run on the 2.7 branch every release.
Also new to this version is a PyPI registration for the 3.1 branch.
One final note I want to make is that the 3.1 branch can be installed side-by-side with the 2.7 branch, as the 3.1 branch calls the 3to2 executable “3to2_31″. I don’t think that I want to change that, but please let me know if this seems like too much of a burden, as I am open to completely turning 3to2 upside-down based on feedback from the (majority of the) community.