profile
viewpoint

Ask questionsSupport for non-standard shells

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> Running code using the "Run Python File in Terminal" icon should support shells outside of pwsh, cmd, etc. If using Powershell, the command is prefixed with &. If using CMD, the command is not prefixed. If using another shell (such as nushell), the command is still prefixed as if it was powershell. This causes the command to fail. image

I have been using the setting "terminal.integrated.shell.windows" for setting the shell to utilize.

microsoft/vscode-python

Answer questions luabud

Hey @kfardanesh! If we were to do it, I believe we'd address https://github.com/microsoft/vscode-python/issues/11812 so that it's possible to configure the shell for running Python files. So I'm closing in favour of that 😊

useful!

Related questions

Auto Scroll in the Jupyter output hot 3
Workspace contains pipfile but pipenv --venv failed hot 2
Can you turn off the Microsoft Python Language Server? hot 2
Unable to debug Python tests (duplicate entries in &#34;env&#34;) hot 2
Jupyter server crashed. Unable to connect. Cannot assign requested address hot 2
Auto Scroll in the Jupyter output hot 2
Unable to run launch targets with newest VS Code Python extension hot 2
Unable to start jupyter python interactive window hot 1
HBox output is not shown correctly in the interactive window hot 1
Debug -> Add Debug Configuration 'Cannot read property openConfigFile' hot 1
VSCode cannot connect to jupyter server; with browser this works fine hot 1
Linux arm64/aarch64 support hot 1
Add setting to disable icon for "Run Python File In Terminal" hot 1
Extension Host keeps crashing hot 1
Activate environment before debugging tests hot 1
Github User Rank List