-
Notifications
You must be signed in to change notification settings - Fork 1.2k
StdErr from ShellExec, stty: stdin isn't a terminal #14938
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
Comments
Thanks for replying this issue Please confirm this option environment is 3.8 and it's a venv |
Please could you open the python output panel and copy the contents from that too, I'm interested in the first 10 lines of the output (to see what experiments this instance of vscode belongs to) |
We have been looking into this issue for a few days now and found that some users managed to get this working switching to the latest version of VSCode insiders. Please could you let us know whether it works for you when you use VSCode insiders. Total help narrow down the problem. |
Thanks for the quick response! To answer your questions:
Yes it's a
Nope same issue with insiders' build 😕 Fwiw I have pyenv-virtualenv installed on my system, but I'm not using that for this virtualenv, and it appears that it shouldn't have an impact; when I open a terminal in VSCode here's what I get: ➜ source /Users/pokey/.venv/flashcards-test/bin/activate
➜ python --version
Python 3.7.3
➜ which python
/Users/pokey/.venv/flashcards-test/bin/python Note that the first line wasn't typed by me, but automatically by VSCode |
I'm having a similar issue when I try to run a jupyter notebook. My error is: I get this error when I try to run bash files through cmd. So I need to do all of my python stuff through the powershell, where I can set the argument to bypass the execution policy. I have set that as the default terminal in my
|
Thanks for the bug report! We just wanted to quickly acknowledge we received it and we will triage this as soon as we can. |
This is a duplicated issue in 15594. And it is already solved. |
When I try to run a cell in a Jupyter notebook, I get the following error:
Environment data
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-11T01:11:34.018Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0
Expected behaviour
The cell runs
Actual behaviour
The error message above
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
Logs
Output for
Jupyter
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toJupyter
)The text was updated successfully, but these errors were encountered: