4 ms·
> 2to3 has worked for an overwhelming number of use cases. And in fact, most code requires very few changes to begin with. That is not at all my experience, no
by dwheeler 6y ago
> 2to3 has worked for an overwhelming number of use cases. And in fact, most code requires very few changes to begin with.
That is not at all my experience, nor is that experience of most other people I've ever talked to.
- __turbobrew__ 6y agoI ran 2to3 on 1 of about 200 modules at my workplace codebase and it took me about an hour to run 2to3 and fix up the leftovers in that module. Now do that for 199 other modules and it becomes much more work than “just run 2to3”.
- joshuamorton 6y agoIn the migration I was a part of (probably one of the larger ones, period), I think something like 90% of code could be migrated by automation. And of the remaining 10, most of it needed only trivial human oversight. That remaining two percent had a lot of painful things (truly, I have some stories), but "the overwhelming number of use cases" was trivial.
- bastawhiz 6y agoI migrated a large codebase with 2to3 and six. It took me half a day. 2to3 did roughly 60-75% of the work and six cleaned up almost all of the rest. It's not foolproof, but it is surely better than nothing. It's perhaps also worth noting that I did this in late 2017. Your experience likely varies depending on when you attempted it.