If you run `jupyter --paths` and `sage -sh <<<"jupyter --paths"` you see the difference in paths. The relevant ones for you are probably the sage-specific ones $SAGE-LOCAL/var/lib/sage/venv-python3.10/share/jupyter Whatever is there will get picked up by sage's jupyter but, naturally, not by your standard jupyter. So the kernels that live there could be copied to a location that is accessed by your system jupyter: $HOME/.local/share/jupyter or something like that.

Note that the files there might need some surgery, because starting those kernels probably needs to happen through sage's python (or at least its venv); similar to how to get the sage kernel working in a system jupyter. On Monday 8 April 2024 at 11:16:45 UTC-7 Emmanuel Charpentier wrote: > Setup : Sage 10.4.beta1 running on Ubuntu 22.04 LTS under WSL2 in Windows > 11 (don’t get me started…). I also installed emacs and its juyter > <https://github.com/emacs-jupyter/jupyter> package, which is able to use > Sage-installed kernels … when emacs is started from the Sage shell. [ Yes, > there is a point to this…] > > What I want to do is to be able to use these Sage-installed kernels from > outside the Sage shell environment, thus avoiding to duplicate the Sage > Jupyter installation. In other words, I want a jupyter command that is > able to finfd the Sage-instaled kernels in their correct environment. > > Is there any way to do that ? > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/92d5f86e-6ab1-40f6-9211-ce2e4c1fbc1en%40googlegroups.com.