Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document/support installation of multiple GAP kernels #95

Open
stevelinton opened this issue Feb 13, 2019 · 1 comment
Open

Document/support installation of multiple GAP kernels #95

stevelinton opened this issue Feb 13, 2019 · 1 comment

Comments

@stevelinton
Copy link

I'd like to have multiple GAP kernels installed, to line up with my multiple installations of GAP (release, master, etc.). I suspect this is not too hard -- presumably just editing a kernel.json file somewhere, but it would be helpful to document how to do it.

@markuspf
Copy link
Member

This needs multiple things to happen;

currently we're using the jupyter-kernel-gap script to even run gap, and that script gets its executable from the environment variable $JUPYTER_GAP_EXECUTABLE or $GAP (in that order).

One way of resolving this is hard-coding the path to the GAP executable into this script, and hard-coding the location of the script into the kernel.json file that is installed.

This means hard coding the location of GAP when installing the kernelspec (one can write a GAP function for this, all one needs to do is adapt the file kernel.json (possibly into a temporary directory) in the JupyterKernel package and then execute jupyter kernelspec install pkg/JupyterKernel/etc/jupyter

See also here on my machine:

# jupyter kernelspec list
Available kernels:
  calysto_scheme    /home/mp397/.local/share/jupyter/kernels/calysto_scheme
  gap-4             /home/mp397/.local/share/jupyter/kernels/gap-4
  gap-native        /home/mp397/.local/share/jupyter/kernels/gap-native
  gap-test          /home/mp397/.local/share/jupyter/kernels/gap-test
  python3           /home/mp397/.local/share/jupyter/kernels/python3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants