representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will on your computer, notebook documents are just files on your local filesystem with a ‘‘.ipynb‘‘ extension. This allows you to use familiar workflows for organizing your notebooks into folders and sharing

resources on creating and distributing packages Example - Server extension Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom documents are internally JSON [https://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open… menu option will

representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled and shared with colleagues. directly, bypassing the dashboard, with jupyter notebook my_notebook.ipynb. The .ipynb extension is assumed if no extension is given. When you are inside an open notebook, the File | Open... menu option will can either be specified in a requirejs module, or registered in a registry, for example when an extension is loaded. This example shows a frontend comm target registered in a registry: Jupyter.notebook