Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom request handlers Custom front-end extensions Customize keymaps Custom bundler the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. Opening a comm from the frontend This is very similar to above protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: originate from pages served by this server (validated with XSRF cookie and token)

Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom request handlers Custom front-end extensions Customize keymaps Custom bundler the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. Opening a comm from the frontend This is very similar to above protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: originate from pages served by this server (validated with XSRF cookie and token)

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token) spec manager class to use. Should be a subclass of jupyter_client.kernelspec.KernelSpecManager. The Api of KernelSpecManager is provisional and might change without warning between this version of Jupyter

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token) spec manager class to use. Should be a subclass of jupyter_client.kernelspec.KernelSpecManager. The Api of KernelSpecManager is provisional and might change without warning between this version of Jupyter

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token) spec manager class to use. Should be a subclass of jupyter_client.kernelspec.KernelSpecManager. The Api of KernelSpecManager is provisional and might change without warning between this version of Jupyter

print "Hello World" console.log("Hello World") And a table like this: | This | is | |------|------| | a | table| A nice HTML Table: This is a table 3.4.6 General HTML Because Markdown is a superset command and edit mode are fully customizable. These customizations are made using the Jupyter JavaScript API. Here is an example that makes the r key available for running a cell: In [ ]: %%javascript Jupyter action no longer be available via the keypress r.” There are a couple of points to mention about this API: • The help_index field is used to sort the shortcuts in the Keyboard Shortcuts help dialog. It defaults

Example - Server extension and nbextension Example - Bundler extension Extending the Notebook Contents API File save hooks Custom request handlers Custom front-end extensions Customize keymaps Custom bundler the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. Opening a comm from the frontend This is very similar to above protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: originate from pages served by this server (validated with XSRF cookie and token)

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to replace the token login mechanism. This can be set to false to prevent changing password from the UI/API. NotebookApp.allow_root [Bool] Default: False Whether to allow the user to run the notebook as root protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token)

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to replace the token login mechanism. This can be set to false to prevent changing password from the UI/API. NotebookApp.allow_root [Bool] Default: False Whether to allow the user to run the notebook as root protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token)

the data in the message This example uses the IPython kernel; it’s up to each language kernel what API, if any, it offers for using comms. 3.2 Opening a comm from the frontend This is very similar to replace the token login mechanism. This can be set to false to prevent changing password from the UI/API. NotebookApp.allow_root [Bool] Default: False Whether to allow the user to run the notebook as root protection Jupyter notebook 4.3.1 introduces protection from cross-site request forgeries, requiring API requests to either: • originate from pages served by this server (validated with XSRF cookie and token)