Vscode-jupyter: Run Python file in terminal context menu missing

[DonJayamanne]

• Open VSC
• Open a python file
• Context menu is missing
• Open another (non python file)
• Go back to the python file
• The context menu is now available

[DonJayamanne]

https://github.com/Microsoft/vscode/issues/65041

[DonJayamanne]

@qubitron we'll need to wait for a VSC release (the fix has not yet been released)

[qubitron]

@anapo14 just hit this issue today, are you sure it was fixed by the upstream issue? VS Code version 1.31.1, Python 2019.2.5433.

[DonJayamanne]

This time, its a different cause.
Enabling the setting Send Selection To Interactive Window is what hides this menu item.

[IanMatthewHuff]

Yeah, it was changed in this PR:
https://github.com/Microsoft/vscode-python/pull/4144/files

I believe that it was intentionally planned at the time (Interactive window would take over from the normal terminal with that setting) but I don't think that it's the right thing. Even if we take over shift-enter we should keep the old context menu commands in there. We've had one customer request already to have the ability both to run selection in the Interactive Window and in the terminal from the same file.

[Hamberfim]

I would like to retain the ability to "Run Selection/Line in Python Terminal" and "Run python file in Terminal" from the content menu as I use these two far more than launching into the interactive Jupyter window. I like the new interactive Jupyter feature and it's location in the right-click content menu but not as a replacement and I would suspect that most of us would prefer to be able to set the shift-enter to our liking without it defaulting back to interactive Jupyter or the inverse if people prefer to set it to the new feature.

[IanMatthewHuff]

@Hamberfim My merge linked in above (it's in our development build now, but not our active release) should put back those two context menus commands regardless of if shift-enter is sent to the Interactive Windows or not. However, in the current state, it does take over the shift-enter hotkey when turned on. To have hotkeys for both "send to interactive window" and "send to terminal" you would have to edit one of them in the keybindings to a new hotkey command. Is that acceptable? From your comment I'm thinking that you actually don't want it to conflict on the hotkey at all.

[Hamberfim]

Thanks @IanMatthewHuff . Yes, that is acceptable and you are correct that I actually don't want it to conflict on the hotkey at all. :D