-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Test: built-in Notebook Variables view #203058
Comments
I got caught by not being able to expand nodes while paused in the debugger. At one point I was thinking that while paused, we might use the debugger to update values. Is that not actually possible, or would you try that at some point? |
We could do that, the extension's view does by delegating to either a debug provider or kernel provider. I was just thinking that the debug variables view already contains all that info, but it is a strange behavior. |
refs: #165445
microsoft/vscode-jupyter#14821
Complexity: 4
Create Issue
Pre-requisites - If you don't have python set up to run notebooks
Create: new jupyter notebook
and runprint(1)
in a cell.a. If the cell runs successfully, you're already set up, otherwise...
A virtual environment should get created in your workspace with all necessary packages installed, and the cell should run successfully.
Testing
The jupyter extension is the only extension with a variable provider at this point, and only for python
"notebook.experimental.variablesView": true,
in settingsNotebook Variables
sectionKnown issues / shortcomings
Improve large collection handling: #203060
More detail in value for collections: microsoft/vscode-jupyter#15056
Keep expanded state persistent: #203067
Don't show the notebook variable view when not applicable: #203068
sample code
simple types
objects
long list
circular reference
The text was updated successfully, but these errors were encountered: