As you can see in the last 3 lines, "no changes" but also "need to be modified". Seems like this is a longstanding issue with 2to3.
I think the "need to be modified" is translated into the rt.files attribute that powers the --enforce flag.
I haven't dug into fissix yet, but maybe it represents a suitable layer at which to undo the damage? If a path says "no changes", remove it from the files list? Just an idea!
Description
Hi there! While trying to enforce 2/3 compatibility on a large codebase, I ran across an issue with modernize's
--enforce
flag:As you can see in the last 3 lines, "no changes" but also "need to be modified". Seems like this is a longstanding issue with 2to3.
I think the "need to be modified" is translated into the
rt.files
attribute that powers the--enforce
flag.I haven't dug into fissix yet, but maybe it represents a suitable layer at which to undo the damage? If a path says "no changes", remove it from the files list? Just an idea!
Details