forked from DonJayamanne/pythonVSCode
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
area-formattingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
Description
Environment data
- VS Code version: 1.47.3
- Extension version (available under the Extensions sidebar): v2020.7.96456
- OS and version: Ubuntu 20.04
- Python version: 3.8.3 (installed by pyenv)
- Type of virtual environment used: pyenv-virtualenv
- Relevant/affected Python packages and their versions: XXX
- Relevant/affected Python-related VS Code extensions and their versions: XXX
- Value of the
python.languageServersetting: doesn't seem to matter; I have tried Jedi, Microsoft, Pylance, and None - isort version: 4.3.21
Expected behaviour
When I hit save on a Python file, I expect it to quickly/automatically sort my imports
Actual behaviour
It pops up a box much like this one:
Saving 'main.py': Applying code action 'Sort imports'.
And that box never goes away. It hangs indefinitely. Obviously it never actually sorts my imports either, nor does it proceed to linting / auto-formatting. It just gets stuck.
Steps to reproduce:
- pip install black pylint isort autoflake
- Copy my settings.json file
- Save a Python file
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
> ~/.pyenv/versions/myproject/bin/python ~/.vscode/extensions/ms-python.python-2020.7.96456/pythonFiles/pyvsc-run-isolated.py ~/.vscode/extensions/ms-python.python-2020.7.96456/pythonFiles/sortImports.py - --diff
cwd: ~/src/myproject/home
> ~/.pyenv/versions/myproject/bin/python ~/.vscode/extensions/ms-python.python-2020.7.96456/pythonFiles/pyvsc-run-isolated.py ~/.vscode/extensions/ms-python.python-2020.7.96456/pythonFiles/sortImports.py - --diff
cwd: ~/src/myproject/home
andrewhead, EthanSteinberg, mattsplats, hardianlawi, iutlu and 20 more
Metadata
Metadata
Assignees
Labels
area-formattingbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug