If I disable shift-enter from sending to the interactive window, shift-enter sends Python code to inappropriate termninals.

[greazer]

From a marketplace review (From: Not Specified on 3/18/2022). Here's the relevant comment:

"So that's a matter of opinion and doesn't necessarily justify one staring something. After all, in theory, if I don't like it I just disable the code that pipes things into notebooks when I hit shift -enter, back to four of five stars.

If you do that, and you have a python terminal running, you'll send (possibly incomplete) code into a python terminal if it is running. If I type exit, though. It'll still send code, to the specific terminal it thinks is the python terminal. Powershell was not amused by print('hello world'). You can even start an ipython kernel and send code in using shift enter to see what a decent cli interface feels like... well, except the fact that it messes up indentation on multiple lines of code. So it both feels like it's covering up a buggy part of the python implementation and it suggests a world where I could just flip on an ipython terminal and use that."

[karrtikr]

Here's the scenario which user describes:

The thing is we cannot know if the Python interactive session in the terminal is exited or not, so we simply keep sending the selection and this is expected.

well, except the fact that it messes up indentation on multiple lines of code

Regarding the support for IPython, we do have #8945 #17172 opened where we plan to help with the indentation issues so users can launch their terminals using IPython instead and would not have this problem. Closing in favor of that. Here's a workaround that can work for the user: #8945 (comment).