You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extension version (available under the Extensions sidebar): v2021.9.1218897484
OS and version: windows 10
Python version (& distribution if applicable, e.g. Anaconda): 3.9
Type of virtual environment used: venv
Relevant/affected Python packages and their versions: black 21.8b0, flake8 3.9.2
Relevant/affected Python-related VS Code extensions and their versions: XXX
Value of the python.languageServer setting: default
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
black formats the file, then flake8 runs on the formatted code, so no formatting errors appear
Actual behaviour
formatter runs, then formatting errors from flake8 appears on the newly formatted code where the errors are no longer there
Steps to reproduce:
note that i can't reliably reproduce this, but if you change autosave to afterDelay it seems to happen much more often
change some code to formatting that black won't like (but still valid syntax)
ctrl+s
wait for the formatter and linter(s) to run
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
We are currently investigating getting linters to work "on change". See #17235 , which should address this problem. So closing this in favor of addressing #408 and #17235
Environment data
python.languageServer
setting: default[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (
python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]Expected behaviour
black formats the file, then flake8 runs on the formatted code, so no formatting errors appear
Actual behaviour
formatter runs, then formatting errors from flake8 appears on the newly formatted code where the errors are no longer there
Steps to reproduce:
note that i can't reliably reproduce this, but if you change autosave to
afterDelay
it seems to happen much more oftenLogs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)The text was updated successfully, but these errors were encountered: