Reusing the Python shell after using quit() will keep running python commands

[andreamah]

Testing #22926

1. Run a command that will open the Python interpreter using shift+enter on a line.
2. Manually run quit() in the python interpreter.
3. Run a command again that will open the Python interpreter using shift+enter on a line.
4. Notice that the interpreter doesn't open 🐛
5. Furthermore, continually running shift+enter will keep adding to the command that it sends to the terminal.

In this case, I kept running time.sleep(1) in step 4 and 5.

This is still in the Python shell, btw.

[anthonykim1]

@karrtikr Is there way we know which Terminal instance(s) have opened/launched Python REPL?

[karrtikr]

No, we can't directly tell if a terminal is a REPL as far as I know.

Although VS Code does give us access to commands run in the terminal. So technically if "quit()" is run, we can know that.

[karrtikr]

Monitoring that may be expensive though, so I suggest only doing it if enough users want this feature.

[github-actions]

Hey @anthonykim1, this issue might need further attention.

@andreamah, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!