We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
cmd
The set of available variables is currently somewhat limited. I suggest adding support for the full set of variables available in VSCode, and which are accessible in e.g. tasks.json (https://code.visualstudio.com/docs/editor/tasks#_variable-substitution). This would e.g. allow using the ${command:python.interpreterPath} variable to write a command to activate the virtual environment, allowing subsequently running any commands that require the virtual environment, thus potentially mitigating #48.
tasks.json
${command:python.interpreterPath}
The text was updated successfully, but these errors were encountered:
Seems like a good idea to me! Would love help with this one.
Sorry, something went wrong.
No branches or pull requests
The set of available variables is currently somewhat limited. I suggest adding support for the full set of variables available in VSCode, and which are accessible in e.g.
tasks.json
(https://code.visualstudio.com/docs/editor/tasks#_variable-substitution). This would e.g. allow using the${command:python.interpreterPath}
variable to write a command to activate the virtual environment, allowing subsequently running any commands that require the virtual environment, thus potentially mitigating #48.The text was updated successfully, but these errors were encountered: