-
Notifications
You must be signed in to change notification settings - Fork 294
Introducing Native Notebooks
Jim Griesmer edited this page Jul 2, 2021
·
16 revisions
Dealing with some small experience issues? See if your issue already exists under our "papercut" label, or create a new one here: Papercut Issues for Notebooks
There are two ways to enable the new experience:
- Use VS code insiders (https://code.visualstudio.com/insiders/). It will pickup an 'insiders' version of the Jupyter Extension that automatically uses the new UI
- Enable the 'NativeNotebookEditor' experiment in your settings.json. This is done by adding these lines below:
"workbench.editorAssociations": {
"*.ipynb": "jupyter-notebook"
},
"jupyter.experiments.optInto": [
"__NativeNotebookEditor__"
],
- Disable the 'NativeNotebookEditor' experiment in your settings.json. This is done by removing these lines:
"workbench.editorAssociations": {
"*.ipynb": "jupyter-notebook"
},
"jupyter.experiments.optInto": [
"__NativeNotebookEditor__"
],
and adding these lines:
"jupyter.experiments.optOutFrom": [
"NativeNotebookEditor"
],
- To create a new notebook open the command palette (Windows: Ctrl + Shift + P, iOS: Command + Shift + P) and select the command
"Jupyter: Create New Blank Jupyter Notebook"
- Contribution
- Source Code Organization
- Coding Standards
- Profiling
- Coding Guidelines
- Component Governance
- Writing tests
- Kernels
- Intellisense
- Debugging
- IPyWidgets
- Extensibility
- Module Dependencies
- Errors thrown
- Jupyter API
- Variable fetching
- Import / Export
- React Webviews: Variable Viewer, Data Viewer, and Plot Viewer
- FAQ
- Kernel Crashes
- Jupyter issues in the Python Interactive Window or Notebook Editor
- Finding the code that is causing high CPU load in production
- How to install extensions from VSIX when using Remote VS Code
- How to connect to a jupyter server for running code in vscode.dev
- Jupyter Kernels and the Jupyter Extension