-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Run Python File in Terminal re-uses an occupied terminal which is not available #85
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
From @half1red on September 7, 2017 7:48 Hi, I think there's two way of seeing this action:
the second one would be a great feature as it would allow one to keep the variables and functions in the kernel and play with them interactively. Today I don't think that is possible. Do you think that would be a feature that could be put in your extension (which is awesome btw)? Thank you for your work ! |
I'd love this personally. I've been wanting some integration with an IPython terminal and VS Code. Jupyter's qtConsole would be better, but IPython is a start for sure. Some auto detect would also be nice as well if possible. Like if it senses that an IPython console is open the it will run in there, but if it senses a standard console it'll just open a new terminal and run the code there. |
First of all: Thanks for your great work. |
We now create a new terminal for your first launch and then subsequently re-use it going forward. This should solve the issue for the OP. |
From @gandhis1 on February 8, 2017 21:33
Steps:
Copied from original issue: DonJayamanne/pythonVSCode#723
The text was updated successfully, but these errors were encountered: