extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

extensions Let’s look at highlights of each area. 4.1 Jupyter’s Common Configuration system Jupyter applications, from the Notebook to JupyterHub to nbgrader, share a common configuration system. The process process for creating a configuration file and editing settings is similar for all the Jupyter applications. • Jupyter’s Common Configuration Approach • Common Directories and File Locations • Language kernels 'zz', handler : function (event) { IPython.notebook.execute_cell(); return false; }} ); core.display.Javascript object> “By default the keypress r, while in command mode, changes the type of

jupyter/custom/custom.js. You can share your custom.js with others. Back to theory [ ]: from jupyter_core.paths import jupyter_config_dir jupyter_dir = jupyter_config_dir() jupyter_dir and custom js is in import io, os, sys, types [ ]: from IPython import get_ipython from nbformat import read from IPython.core.interactiveshell import InteractiveShell Import hooks typically take the form of two objects: 1 is pywin32. • Issues surrounding the creation of the kernel’s communication file utilize jupyter_core’s secure_write() function. This function ensures a file is created in which only the owner of the

jupyter/custom/custom.js. You can share your custom.js with others. Back to theory [ ]: from jupyter_core.paths import jupyter_config_dir jupyter_dir = jupyter_config_dir() jupyter_dir and custom js is in import io, os, sys, types [ ]: from IPython import get_ipython from nbformat import read from IPython.core.interactiveshell import InteractiveShell Import hooks typically take the form of two objects: 1 is pywin32. • Issues surrounding the creation of the kernel’s communication file utilize jupyter_core’s secure_write() function. This function ensures a file is created in which only the owner of the

jupyter/custom/custom.js. You can share your custom.js with others. Back to theory [ ]: from jupyter_core.paths import jupyter_config_dir jupyter_dir = jupyter_config_dir() jupyter_dir and custom js is in import io, os, sys, types [ ]: from IPython import get_ipython from nbformat import read from IPython.core.interactiveshell import InteractiveShell Import hooks typically take the form of two objects: 1 is pywin32. • Issues surrounding the creation of the kernel’s communication file utilize jupyter_core’s secure_write() function. This function ensures a file is created in which only the owner of the

jupyter/custom/custom.js. You can share your custom.js with others. Back to theory [ ]: from jupyter_core.paths import jupyter_config_dir jupyter_dir = jupyter_config_dir() jupyter_dir and custom js is in import io, os, sys, types [ ]: from IPython import get_ipython from nbformat import read from IPython.core.interactiveshell import InteractiveShell Import hooks typically take the form of two objects: 1 is pywin32. • Issues surrounding the creation of the kernel’s communication file utilize jupyter_core’s secure_write() function. This function ensures a file is created in which only the owner of the