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
I'm not sure if I'm missing something, but I cannot find an option to restart the native REPL. If I just close the pane and then send another Python statement (Shift-Enter), it gets executed in the previously started native REPL (i.e., all created object in that session will still be available).
The text was updated successfully, but these errors were encountered:
Interesting, I can't seem to repro this.
If you close the REPL tab via clicking on the x icon, It should launch new REPL for you when you try to send command again.
Could you try "Python Clear cache and reload" and see if that helps?
Also make sure it says "Python REPL" on the top right corner.
Here is what happens for me on the latest version of vscode insider and python extension.
No, this does not work for me. When I close the Native REPL tab and run a new command, it opens the previous REPL (in this example, x should not exist in a new REPL, but apparently this is still the same session):
Screen.Recording.2024-11-04.at.15.41.22.mov
When I run "Python: Clear Cache and Reload Window", the native REPL session is indeed closed and a new one is started. However, I don't think this is intended, as the REPL should either close when closing the tab or when selecting a dedicated "Trash" action (which does not exist, but this is how the integrated terminal works, so I think the native REPL should behave similarly).
anthonykim1
changed the title
Add option to restart native REPL
Native REPL wrongly caches state from previous session
Dec 10, 2024
I'm not sure if I'm missing something, but I cannot find an option to restart the native REPL. If I just close the pane and then send another Python statement (Shift-Enter), it gets executed in the previously started native REPL (i.e., all created object in that session will still be available).
The text was updated successfully, but these errors were encountered: