Support IPython for Shift+Enter (execute line in terminal)

Discussed in https://github.com/microsoft/vscode-python/discussions/16744

<div type='discussions-op-text'>

^{Originally posted by sergeyf July 20, 2021}

Environment data

• VS Code version: 1.58.2
• OS and version: Windows_NT x64 10.0.19043
• Python version (& distribution if applicable, e.g. Anaconda): 3.9,1
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
• Value of the python.languageServer setting: pylance-2021.7.4

Expected behaviour

Pressing Shift + Enter copies code to the terminal and executes it

Actual behaviour

Pressing Shift + Enter copies code to the terminal but it doesn’t execute

Steps to reproduce:

</div>

EDIT: https://github.com/microsoft/vscode-python/issues/18177 could resolve this.

[DEVNULLDNE]

I have this problem off and on as well. You can get around it if you have the multi-command extension by adding the following to your keybindings.json:

    {
        "key": "shift+enter",
        "command": "-python.execSelectionInTerminal",
        "when": "editorTextFocus && !findInputFocussed && !jupyter.ownsSelection && !notebookEditorFocused && !replaceInputFocussed && editorLangId == 'python'"
    },
    {   // use this when ipython gets borked using "python.execSelectionInTerminal"
        "key": "shift+enter",
        "command": "extension.multiCommand.execute",
        "args": {
            "interval": 40,
            "sequence": [
                "python.execSelectionInTerminal",
                "workbench.action.terminal.focus",
                "workbench.action.terminal.scrollToBottom",
                {"command": "workbench.action.terminal.sendSequence",
                    "args": { "text": "\u000D" }}, // this basically "presses enter"
                "workbench.action.focusActiveEditorGroup"
            ]
        },
        "when": "editorTextFocus && !findInputFocussed && !replaceInputFocussed && editorLangId == 'python'"
    },

I stole the solution from here with some slight modifications. Mostly adding an interval as the commands were happening too quickly sometimes.

[ryan-feeley]

This issue is funny, because sometimes I get the desired behavior already, and sometimes I don’t, depending on my conda environment.

Environment A from CONDA-FORGE: This environment gives me the normal behavior where code is copied and properly executed: conda create --name py37A --channel conda-forge python=3.7 ipython ipykernel

So if I highlight the following and do shift+enter:

x = 5

y = x**2

def squareIt(x):
    return x**2

The IPython console looks like this:

In [1]: x = 5

In [2]: y = x**2

In [3]: def squareIt(x):
   ...:         return x**2
   ...: 

In [4]: 

Environment B from DEFAULTS (Anaconda): This environment gives me the bug behavior where code is copied but not executed: conda create --name py37B --channel defaults python=3.7 ipython ipykernel

So if I highlight the following and do shift+enter:

x = 5

y = x**2

def squareIt(x):
    return x**2

The IPython console looks like this:

In [1]: x = 5
   ...: y = x**2
   ...: def squareIt(x):
   ...:     return x**2
   ...: 
   ...: 

I’m on Windows 10, and the latest install of VSCode, but no insiders channel, or similar.

I don’t know if the difference in behavior is from the conda-forge channel having slightly newer packages, or from some deeper differences. Updating the prompt_toolkit package in Environment B from the conda-forge channel (which updates several dependencies) is enough to allow that environment to have the “no bug expected behavior”.