[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

Change by Irit Katriel : -- stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

Irit Katriel added the comment: If I understand correctly, this is not about an observed bug but about a confusion about which log_error function is being called. Can we close this or is there something to do here? -- nosy: +iritkatriel resolution: -> not a bug status: open -> pendi

[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

Karthikeyan Singaravelan added the comment: Thanks Nick for the details. I think 2to3 uses StdoutRefactoringTool [1] which inherits from RefactoringTool in the chain and implements log_error [2] that logs the error. StdoutRefactoringTool inherits from MultiprocessRefactoringTool [3] which i

[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

Change by Terry J. Reedy : -- nosy: +benjamin.peterson versions: -Python 3.4, Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue32750] lib2to3 log_error method behavior is inconsitent with documentation

New submission from Nick Smith : The log_error method in refactor.RefactoringTool raises the exception: def log_error(self, msg, *args, **kwds): """Called when an error occurs.""" raise but every usage of it implies that it does not, e.g: def refactor_string(self, data,