On Tuesday, December 22, 2015 at 9:16:55 PM UTC+1, Nils Bruin wrote: > > We could make the UX more consistent by "preinstalling" a migration ipy > notebook. >
Into which directory are we going to put that MigrateFromSagenb.ipynb file? > In fact, that notebook could include code to open and read the sagenb > worksheets (jupyter kernels don't run chrooted by default, right? so their > code can still access HOME/.sagenb) > The kernel and the file browser ui are two separate components, potentially running on separate computers. The kernel can execute arbitrary code (and access ~/.sage if the OS allows), the file browser is restricted to the directory tree below the startup directory. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
