Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"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

Comments

@DetachHead
Copy link

when pressing F1 and run "Select and run tox environment", the following error appears:

image

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

@awecx
Copy link

awecx commented Mar 21, 2024

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.interpreter options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants