The second question I’ve been asked it about Jupyter being turned into JupyterLabs (the first was “how do I upload files”).
I found this question/answer and quickly installed jupyterlab in the appropriate module and implemented the check mark on the form and there it is. Fantastic - thank you.
My question is about kernels. I understand the end point, but I don’t know enough about JupyterLab and kernels, and I’m not confident of my reading of the ruby in template/script.sh.erb
From what I can tell, the process is:
- get Jupyterlab work (tick)
- prepare various other installations in their own modules (R, Scala, Julia, Python etc)
- load the modules within the
template/script.sh.erb
?
My primary concern is conflicting python modules (for instance). Am I correct in thinking that the JupyterLab will remain in the env it is launched in (for eg /usr/local/modules/ood-jupyter
), but each of the kernels will launch their own self contained envs (for eg /usr/local/modules/python27
) when they are chosen and launched?
ie, lines 84~170 ish are building menu items, which are triggered when they are chosen?