[issue41655] New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by

Change by Gregory P. Smith : -- resolution: -> wont fix stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue41655] New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by

Gregory P. Smith added the comment: I expect your overall logic is sound in the PR. But this is a public API change, and while we've typically exempted lib2to3 from needing to concern itself about deprecations and API changes by leaving it undocumented and explicitly promising not to care

[issue41655] New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by

Chrome added the comment: you can run example.py to reproduce this bug. -- Added file: https://bugs.python.org/file49434/example.py ___ Python tracker ___

[issue41655] New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by

Change by Chrome : -- versions: +Python 3.5, Python 3.6, Python 3.7, Python 3.8, Python 3.9 ___ Python tracker ___ ___

[issue41655] New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by

Change by Chrome : -- title: new Node may not visited in lib2to3.refactor.RefactoringTool.traverse_by -> New Node may not be visited in lib2to3.refactor.RefactoringTool.traverse_by ___ Python tracker