Jim Griesmer
Jim Griesmer
For sure, we need to make sure that when the user gets the notification that they can use the interactive window on shift-enter that the interactive window is not invoked...
Should rename the menu item too to be more specific about what it's doing.
Really creative and interesting! Given the above you could take it to the next step and create a snippet. 1. Ctrl+Shift+P -> Preferences: Configure User Snippets 2. Pick a snippet...
@jaymegordo, thanks for the feedback! This is a tough call to make. Can you take a couple minutes to describe why you prefer this behavior?
Hi @AeneasZhu, we have been mulling over additional changes to the debugging experience for the interactive window and this suggestion is on our radar again. However, I'd like some clarification....
I'm reproing this right now using VS Code 1.61-insiders and the latest Jupyter insiders extension.
More specifically, I chose: ```File->Convert Notebook to Python Script``` and I get an export error: ```Info 2021-09-21 13:34:57: Process Execution: > ~\AppData\Local\Programs\PythonCodingPack\python.exe -m jupyter nbconvert --version > ~\AppData\Local\Programs\PythonCodingPack\python.exe -m jupyter...
We should look at the telemetry of the use of this setting.
Enhancement because this is something we'd need to add to the extension to parse the output in order to display something that looks nicer.
In the meantime while we're investigating, you can rollback to the old implementation with this setting: ``` "jupyter.enableNativeInteractiveWindow": false ```