VS Code Insiders don't run the cell with shift+Enter in a .py file with #%% cell separators

[sergei3000]

Does this issue occur when all extensions are disabled?: Yes/No
It's not possible to use this functionality without the MS Jupyter extension. And only the Insiders version is affected.

• VS Code Version: Insiders 1.93.0-insider (Universal)
• OS Version: MacOS Sonoma 14.5 (23F79)

Steps to Reproduce:

1. Install VS Code Insiders
2. Install Python and Jupyter extensions by Microsoft (the release ones)
3. Create a .py file with cell separators like # %% and some code inside a cell
4. Step into the cell
5. Try to run the cell with shift+Enter like in the regular non-insiders version
6. Instead of the "Interactive" window with the set environment (I use conda, install ipykernel into my env), like it works in the regular non-inseder version of vscode, it opens a "Python REPL" window and runs the current line instead of the entire cell. And the environment is something different, I can see it from the fact that it errors out on the line import pandas as pd with ModuleNotFoundError: No module named 'pandas' although pandas is installed in the projects environment.

P.S. The keyboard shortcuts seem to be the same for shift+Enter when I look at them and compare in the regular vscode and in the insiders version.

[amunger]

Do you have "jupyter.interactiveWindow.textEditor.executeSelection": true set in your settings?
Settings don't carry across insiders <> stable, so maybe it just didn't ever get set?

[amunger]

ah, but with # %% code cells, shift+enter should probably just execute the jupyter cell.
@anthonykim1 - we should consider adding !jupyter.hascodecells to the when clause for python.execInREPL

[anthonykim1]

Moving this to Python repo -

[anthonykim1]

Just testing this out - everything works fine with cells with # %% but trying to shift+enter on any other code not surrounded by # %% fails to be executed in both IW nor native REPL.

Tried to locally add !jupyter.hascodecells inside execInREPL for Python extension gave me no luck :/

If there are instances of # %%, should every shift+enter of code(even code block that are outside of # %%) be sent to interactive window? @amunger

[amunger]

created a new issue for that - I think that was existing behavior and kind of an edge case