On September 1, 2025 8:04:47 PM CDT, Kwankyu Lee <[email protected]> wrote:
>
>
>I am pretty sure that it was not created just for that reason, and that it
>does things which the jupyter command does not du (such as make sure that
>threejs is availabe.).
in 2015 jupyter was pretty new, and Sage code,
written by Volker, converted what was there for ipython to jupyter. Maybe he
remembers why it went this way.
Perhaps "jupyter kernelspec install" was just not available then.
>
>
>Moreover it solved the problem of copying the massive sage documentation
>when the kernel is installed, by symlinking instead.
symlinking is flaky across VMs and filesystems. E.g. if you run Jupyter in a
Windows browser (or in VSCode), with Sage running in WSL, then it seems to me
one cannot avoid "jupyter kernelspec install".
Well, yes, it's about 2.3Gb of data, but with the current capacity and cost of
SSDs it's not something to worry about.
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/sage-release/3999C4BC-DD71-4C69-80DF-E63031090114%40gmail.com.
