Open herring-swe opened 7 months ago
This behaviour is part of what autopep8 does on the pycodestyle side when it runs pycodestyle. It is difficult to fix on the autopep8 side.
The first step in addressing this issue is to remove configuration options not supported by pycodestyle from the configuration file.
autopep8 outputs some warnings and verbose messages to stdout instead of stderr. This leads to problems when someone (such as vscode extension vscode-autopep8) wants to format not using --in-place flag since there's no distinction between output code and processing messages and thus writes the message into the new code.. See: https://github.com/microsoft/vscode-autopep8/issues/201
Command Line and Configuration
~/.config/pycodestyle
Command Line
Your Environment