[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Éric Araujo added the comment: This feature is implemented in distutils2. -- components: -Distutils resolution: -> out of date stage: unit test needed -> committed/rejected status: open -> closed versions: -Python 3.1, Python 3.2 ___ Python tracke

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Changes by Éric Araujo : -- assignee: tarek -> eric.araujo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Changes by Éric Araujo : -- components: +Distutils2 -2to3 (2.x to 3.0 conversion tool) stage: -> unit test needed versions: +3rd party, Python 3.2 -Python 3.0 ___ Python tracker

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Changes by Éric Araujo : -- nosy: +Merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Changes by Tarek Ziadé : -- priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

Lennart Regebro added the comment: Also, the run_2to3 method takes the explicit parameter, but does not pass it into the DistutilsRefactoringTool. -- ___ Python tracker ___ _

[issue5616] Distutils 2to3 support doesn't have the doctest_only flag.

New submission from Lennart Regebro : The run_2to3 method, and therefore also the Mixin2to3 class doesn't take a parameter for doctest_only parameter that refactor has. That means you have to do a lot of code duplication if you want to write distutil commands that handle doctest files. The fix i