You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
when I press SHIFT + ENTER, or right click selection -> Run Python -> run selection/line in the python terminal it opens 2 terminals #21393
when I press SHIFT + ENTER, or right click selection -> Run Python -> run selection/line in the python terminal it opens 2 terminals named Python, where the first one opens the python terminal (PID 29056) but the second (PID 434444) does not. After that, it tries to execute the highlighted code in the second terminal which obviously is yielding an error.
If I kill the second Python terminal (PID 434444) and try to run a line of Python again, it opens a new terminal with a new PID and no Python console and behaves exactly like the second one.
If I kill the first terminal and then run the line it does not create another console, but still not running the code.
Finally, if I type python in the second console it opens the python terminal, and if I start running line-by-line execution it works.
Extension version: 2023.10.0
VS Code version: Code 1.79.0 (b380da4ef1ee00e224a15c1d4d9793e27c2b6302, 2023-06-07T14:26:35.552Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz (8 x 2304)
I have got the same issue after I upgraded to v2023.10.0.
When trying to run the selected codes by pressing Shift + Enter -> end up with two terminal windows open:
The first terminal window just activates Python and no follow-up executing the selected codes.
The second terminal is just the default terminal with those Python codes with no python environment.
I just wanted to quickly apologize for the breakage! #21418 has been opened to revert this new terminal feature to fix this breakage. Unfortunately none of our pre-release users ran across this (been in main since May 10, so available in pre-release since May 11; obviously if anyone here is interested in using pre-release versions, more help is always appreciated 😁), and we seem to have a gap in our tests around this flow (which I have opened #21420 to fill that gap).
Our hope is to have a bugfix release out today or tomorrow depending on how the revert PR goes.
Activity
lux5 commentedon Jun 10, 2023
I have got the same issue after I upgraded to v2023.10.0.
When trying to run the selected codes by pressing Shift + Enter -> end up with two terminal windows open:
Version: 1.79.0 (user setup)
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:26:35.552Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.18363
Lauler commentedon Jun 10, 2023
Same issue on Linux/Ubuntu.
Version: 1.79.0
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:28:44.251Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.15.0-73-generic
selgamal-telnyx commentedon Jun 11, 2023
same issue windows 11, reported here with all details
KatlehoJordan commentedon Jun 11, 2023
microsoft/vscode#184790 (comment)
As someone tipped you there, try rolling back to v2023.8.0 of the vscode-python extension.
Some bug appeared in the latest version, it seems.
dirk2011 commentedon Jun 11, 2023
Have this bug also.
Version: 1.79.0
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:28:44.251Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.4.0-150-generic
chrigraf commentedon Jun 11, 2023
Same here:
Version: 1.79.0 (user setup)
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:26:35.552Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19045
starball5 commentedon Jun 11, 2023
Related on Stack Overflow:
If you have the privilege level to do so, help with closing duplicates would be appreciated, so the answers can be put in one place instead of scattered about.
ctedja commentedon Jun 12, 2023
Was also facing this issue. Rolling back to v2023.8.0 seemed to help.
Noath2302 commentedon Jun 12, 2023
same issue for me, thank you starball (@starball5), rolling back really helps
IAmMalteC commentedon Jun 12, 2023
Same issue here. Rollback helps
smoudour commentedon Jun 12, 2023
Same issue here, Windows 10. Rolling back to v2023.8.0 seems to work.
emillykkejensen commentedon Jun 13, 2023
Same here:
Version: 1.79.0 (user setup)
Commit: b380da4ef1ee00e224a15c1d4d9793e27c2b6302
Date: 2023-06-07T14:26:35.552Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621
brettcannon commentedon Jun 13, 2023
I just wanted to quickly apologize for the breakage! #21418 has been opened to revert this new terminal feature to fix this breakage. Unfortunately none of our pre-release users ran across this (been in
mainsince May 10, so available in pre-release since May 11; obviously if anyone here is interested in using pre-release versions, more help is always appreciated 😁), and we seem to have a gap in our tests around this flow (which I have opened #21420 to fill that gap).Our hope is to have a bugfix release out today or tomorrow depending on how the revert PR goes.
4 remaining items
Revert: Run in dedicated terminal feature due to regressions (#21418)
Revert: Run in dedicated terminal feature due to regressions (microso…
Revert: Run in dedicated terminal feature due to regressions (#21427)
karthiknadig commentedon Jun 14, 2023
This fix is out. Stable users v2023.10.1 (latest stable) and for insiders users it is v2023.11.11651007 (latest insiders)