Two shortcuts to run current selection/line?

[cbrnr]

In the keyboard shortcuts preferences, there are two shortcuts that seem to do the same thing:

• Python: Run Selection/Line in Python REPL
• Python: Run Selection/Line in Python Terminal

Both are set to Shift-Enter (I think this is even the default).

I have no idea what the difference between these two commands is, as they seem to do exactly the same thing. However, only the second command actually does what it is supposed to do (opens the terminal tab, starts the interactive interpreter, and runs the command). The first one does not start an interactive interpreter, but just pastes the current selection/line into the terminal (which is running PowerShell on Windows, so it produces an error).

Could someone explain what these two commands actually do?

[cbrnr]

I have not changed any configuration settings, but it seems like there are two separate shortcuts depending on Native REPL being enabled or disabled (the default). Would it be possible to just use a single shortcut (e.g. "Python: Run Selection/Line in Python Terminal") for both settings? The "Native REPL" setting already determines which REPL (native or terminal) will be used, or no?

[anthonykim1]

Hello @cbrnr!
First of all, I appreciate your presence here and all the feedbacks you previously gave to the Python extension.

You are correct that there could be two functionality (from Python extension) in regards to shift+enter.
Which are:

• Python: Run Selection/Line in Python REPL
• Python: Run Selection/Line in Python Terminal
  that you mentioned.

The difference between these two command is that they are supposed to send your Python code to REPL of your choice - The "Run in Python REPL" should run code in editor based new experimental VS Code Native REPL, whereas the Run in Python Terminal is supposed to run your code in Terminal (the traditional interactive interpreter with >>> on the bottom panel)

These should be most clearly explained here: https://code.visualstudio.com/docs/python/run#_interactively-running-python-code

The two options(of run in Python REPL and run in Python Terminal REPL) should not be doing the same thing (if it is, then it would be a bug :/) But please note your workspace setting will effectively override user setting so when you toggle native repl setting to on/off, try to make sure the two (user and workspace) setting align.

And yes you are right on the "native repl" will be the only place as of now to decide which REPL to send your Python code to.
If you can not send to native repl after aligning user and workspace setting to enable native repl, please file an issue and directly tag me. I would like to investigate further.

The experimental native repl was designed to provide more functionality over the traditional interactive interpreter in a way that it provides intellisense, syntax highlighting, autocompletion, variable pane, etc. If you have tried the native repl, I would love to know what you think about it. Its perfectly fine if you still prefer the REPL in terminal, but I would just love to know why so we can take this into future development plans.

I also saw you were using VS Code and Python extension for teaching, so I would be very curious what your students think of this new experimental native repl as well :)

Thanks.

[cbrnr]

Thanks for your reply @anthonykim1! My issue with the two different shortcuts is that their functionality is entirely determined by the "Use Native REPL" setting. If this setting is disabled (the default), only "Python: Run Selection/Line in Python Terminal" works. If this setting is enabled, only "Python: Run Selection/Line in Python REPL". I think this is confusing, so I suggest to merge this shortcut into a single shortcut. This shortcut could be named "Python: Run Selection/Line in Python REPL", because the interactive interpreter running in the terminal is also a REPL.

I'm happy to provide feedback on both the native and standard REPL experience (I actually have several points that are a constant source of confusion for my students and myself), but this is probably not the right place, since I would like to keep this discussion focused on the shortcut confusion. Should I open a new issue or discussion? Or should I PM you?