-
Notifications
You must be signed in to change notification settings - Fork 300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make Jupyter -> Send Selection to Interactive Window, true by default (iff Python stops auto-installing the Jupyter extension). #6565
Comments
This hurts new interactive window users the most because shift+enter will go to the terminal instead of the interactive window |
This functionality was removed when the Jupyter functionality was moved out of the Python extension and into it's own. This was the commit id: 8f50e87. Rather than re-add the prompt, we can consider making the jupyter -> Send Selection to Interactive Window true by default, if and when the Python extension removes installing Jupyter by default. |
jupyter.ownsSelection
prompt missing
Blocked on microsoft/vscode-python#18073 |
is the idea here that if users clicked "shift+enter" we'd prompt them to install the Jupyter extension? |
No actually when/if the python extension removes the jupyter extension as an optional dependency, we're going to switch this setting to true:
|
got it, thanks for the clarification! |
It seems we didn't switch |
We shouldn't override that functionality as long as Python still depends on this extension: microsoft/vscode-python#18073 |
I think the current functionality is good - if the file has a # %% cell in it, it will be sent to the IW, we can add a launch configuration as well to make run in IW more discoverable |
This prompt is used to configure whether shift+enter sends selections in Python files to the terminal or interactive window. Looks like it's been removed entirely (no references in either Python or Jupyter extension).
The text was updated successfully, but these errors were encountered: