You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having the init_cell plugin enabled when opening an untrusted notebook will warn that it will not run the cells automatically, even though there are no initialization cells.
I provide my students with Jupyter through a JupyterHub and have added this extension by default as it could help me streamline distribution of material to them. My students will not know about this plugin, and I wan't to keep it that way unless there is a need for them to know about it.
I'll try make a PR fixing this as well as allowing them to run the code manually by clicking a button in the dialog.
The text was updated successfully, but these errors were encountered:
* FIXESipython-contrib#1223 - Only shows the dialog about untrusted notebooks if there was any initialization cells in it.
* UX improvement - Allows user to run the code directly from the dialog with an additional button "Run code anyway".
consideRatio
added a commit
to consideRatio/jupyter_contrib_nbextensions
that referenced
this issue
Feb 4, 2018
* FIXESipython-contrib#1223 - Only shows the dialog about untrusted notebooks if there was any initialization cells in it.
* UX improvement - Adding a button to trust the notebook through the dialog.
Having the init_cell plugin enabled when opening an untrusted notebook will warn that it will not run the cells automatically, even though there are no initialization cells.
I provide my students with Jupyter through a JupyterHub and have added this extension by default as it could help me streamline distribution of material to them. My students will not know about this plugin, and I wan't to keep it that way unless there is a need for them to know about it.
I'll try make a PR fixing this as well as allowing them to run the code manually by clicking a button in the dialog.
The text was updated successfully, but these errors were encountered: