[Python-Dev] Can someone check my lib2to3 change for fix_imports?

["Martin v. Löwis"]

> But distutils currently *doesn't* invoke it, AFAICT

Sure. In 3k, look at Lib/distutils/command/build.py:build_py_2to3.

That's how I ported Django to Py3k.

> 1) People are currently confused as to where they should be commit fixes.

Sure, but it only happens rarely.

> 2) Changes to the sandbox version have to be manually merged into the
> stdlib version, which is more overhead than I think it's worth. In
> addition, the stdlib version lags the sandbox version.

It's not a real problem, IMO, using msgmerge is fairly straight-forward.

> 3) At least one bug report (issue3131) has mentioned problems with the
> stdlib 2to3 exhibiting problems that the stand-alone version does not.
> This is again extra overhead.

I think the 2to3 packaging issue is otherwise unresolved. Do you want
2to3 to be excluded completely from 2.6 and 3.1 releases? If not,
how do you want them packaged? Will it work if packaged in that way?

> 4) The test_imports test was commented out because of stdlib test
> policy. I'd rather not have that policy imposed on 2to3.

It would be possible to comment out the test only in the copy in the
stdlib version, or to omit testing 2to3 in the stdlib altogether,
if that helps.

Regards,
Martin