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
"Command failed: tox -a 'tox' is not recognized as an internal or external command, operable program or batch file." error when attempting to run any tox commands
#37
Open
DetachHead opened this issue
Mar 4, 2024
· 1 comment
when pressing F1 and run "Select and run tox environment", the following error appears:
this may be caused by the fact that tox is installed inside my pdm project's venv, not globally. if that's the case, it should use vscode's python interpreter path to locate the tox executable. this is how most other extensions work
The text was updated successfully, but these errors were encountered:
I believe it should also be able to run test from an arbitray path (even outside the interpreter).
Many tools support both. For instance black defines the black-formatter.path and black-formatter.interpreteroptions.
when pressing
F1
and run "Select and run tox environment", the following error appears:this may be caused by the fact that tox is installed inside my pdm project's venv, not globally. if that's the case, it should use vscode's python interpreter path to locate the
tox
executable. this is how most other extensions workThe text was updated successfully, but these errors were encountered: