[issue13316] build_py_2to3 does not convert when there was an error in the last run

Éric Araujo added the comment: Closing this. It was not fixed when it would have been useful, and people mostly use other tools that distutils for packaging and 2to3 for transition. -- resolution: -> wont fix stage: test needed -> resolved status: open -> closed

[issue13316] build_py_2to3 does not convert when there was an error in the last run

Éric Araujo added the comment: > It does stop with an error message. But when I reinvoke the command, > converting is > skipped (because the file is already copied). Then that’s the bug: In case of error, the file in the build dir should be removed. By the way, I think this was not reported

[issue13316] build_py_2to3 does not convert when there was an error in the last run

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue13316] build_py_2to3 does not convert when there was an error in the last run

simohe added the comment: It does stop with an error message. But when I reinvoke the command, converting is skipped (because the file is already copied). No error message is raised and the build continues with the remaining jobs (build_*). It should reexecute at least the failing conversion a

[issue13316] build_py_2to3 does not convert when there was an error in the last run

Éric Araujo added the comment: > When I use build_py_2to3 and there is an error while converting a > file with 2to3, convert is skipped on the next run. I think build should stop with an error message if 2to3 fails. Do you agree? -- assignee: -> tarek components: +Distutils, Distutil

[issue13316] build_py_2to3 does not convert when there was an error in the last run

Changes by simohe : -- title: build_py_2to3 does not execute when there was an error before -> build_py_2to3 does not convert when there was an error in the last run type: behavior -> ___ Python tracker _