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
@04Samir From the logs it looks like the "importStrategy": "useBundled", (default) set it to "fromEnvironment" for the extension to use the one from your environment.
If you want to set path you can do it like this: "autopep8.path": ["${workspaceFolder}/.venv/scripts/autopep8.exe"] or "autopep8.path": ["${interpreter}", "-m", "autopep8"]
Diagnostic Data
3.12.5
.venv
Windows 11
v2024.0.0
Behaviour
Expected Behavior
If I installed
autopep8
viapip
, either in my.venv
or globally inPATH
, it should use thatautopep8
version.Actual Behavior
It uses the version that comes with the extension,
v2.1.0
.Reproduction Steps:
Add the following in your workspace's
.vscode/settings.json
:Logs:
Click here for detailed logs
Outcome When Attempting Debugging Steps:
Did running it from the command line work? Yes, running
autopep8 <path-to-file>
in my.venv
's terminal uses the version installed bypip
.Extra Details
isort
main.py
,pyproject.toml
, ... ,.vscode/
,src/*.py
No
.vscode/settings.json
The text was updated successfully, but these errors were encountered: