VScode run code selection

Question

I just made the transition from Spyder to VScode for my python endeavours. Is there a way to run individual lines of code? That's how I used to do my on-the-spot debugging, but I can't find an option for it in VScode and really don't want to keep setting and removing breakpoints.

Thanks.

Answer 1

If you highlight some code, you can right-click or run the command, Run Selection/Line in Python Terminal .

We are also planning on implementing Ctrl-Enter to do the same thing and looking at Ctr-Enter executing the current line .

Answer 2

You can:

1. open a terminal at Terminal>New Terminal
2. Highlight the code you want to run
3. Hit Terminal>Run Selected Text

As for R you can hit CTRL Enter to execute the highlighted code. For python there's apparently no default shortcut (see below), but I am quite sure you can add yours.

Answer 3

In my ver of VSCode (1.25), shift+enter will run selection. Note that you will want to have your integrated terminal running python.

Answer 4

One way you can do it is through the Integrated Terminal. Here is the guide to open/use it: https://code.visualstudio.com/docs/editor/integrated-terminal

After that, type python3 or python since it is depending on what version you are using. Then, copy and paste the fraction of code you want to run into the terminal. It now has the same functionality as the console in Spyder. Hope this helps.

Answer 5

I'm still trying to figure out how to make vscode do what I need (interactive python plots), but I can offer a more complete answer to the question at hand than what has been given so far:

1- Evaluate current selection in debug terminal is an option that is not enabled by default, so you may want to bind the 'editor.debug.action.selectionToRepl' action to whatever keyboard shortcut you choose (I'm using F9). As of today, there still appears to be no option to evaluate current line while debugging, only current selection.

2- Evaluate current line or selection in python terminal is enabled by default, but I'm on Windows where this isn't doing what I would expect - it evaluates in a new runtime, which does no good if you're trying to debug an existing runtime. So I can't say much about how useful this option is, or even if it is necessary since anytime you'd want to evaluate line-by-line, you'll be in debug mode anyway and sending to debug console as in 1 above. The Windows issue might have something to do with the settings.json entry

"terminal.integrated.inheritEnv": true,

not having an affect in Windows as of yet, per vscode documentation.