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

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

primitives 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 venv\lib\site- packages\jupyter_core\paths.py", line 424, in secure_write win32_restrict_file_to_user(fname) File "c:\users\jovyan\python\myenv.venv\lib\site- packages\jupyter_core\paths.py", line 359, in e- packages\jupyter_core\paths.py", line 435, in secure_write win32_restrict_file_to_user(fname) File "C:\Users\jovyan\AppData\Roaming\Python\Python37\site- packages\jupyter_core\paths.py", line 361,

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

primitives 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 venv\lib\site- packages\jupyter_core\paths.py", line 424, in secure_write win32_restrict_file_to_user(fname) File "c:\users\jovyan\python\myenv.venv\lib\site- packages\jupyter_core\paths.py", line 359, in e- packages\jupyter_core\paths.py", line 435, in secure_write win32_restrict_file_to_user(fname) File "C:\Users\jovyan\AppData\Roaming\Python\Python37\site- packages\jupyter_core\paths.py", line 361,