-
-
Notifications
You must be signed in to change notification settings - Fork 490
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 installing sagemath kernel without copying documentation #31620
Comments
comment:1
The procedure to follow would be something like:
We may want to check/refine these instructions to be a little more robust and/or appropriate for other operating systems, but having this documented in an easily discovered place would help. These instructions should probaly be placed or linked to in |
comment:2
See also previous discussions in #30298 |
comment:3
Replying to @nbruin:
For this first step, I think we may want to add an option to the |
New commits:
|
Author: Nils Bruin |
Commit: |
comment:6
Replying to @mkoeppe:
I don't think it's something people need to do very often, so they'd need to look up how to do it anyway. As long as it's easily discovered and a readily copy-pastable formula, I don't think it's so bad if it's a little long. At least it's transparent what is going on for someone with generic bash skills. Let's first get this documented. It's a safe and easy change, so we can still include it in 9.3. Then it'll be up on |
comment:7
OK, that's fine with me. |
Reviewer: Matthias Koeppe |
Changed branch from u/nbruin/document_installing_sagemath_kernel_without_copying_documentation to |
Follow up to #30476: Using
jupyter kernelspec
to installsagemath
kernel results in copying about 2Gb of documentation into the jupyter kernels share directory. That's generally not the spot to put large files/documentation. Document how to avoid this.Component: documentation
Author: Nils Bruin
Branch/Commit:
79914c2
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/31620
The text was updated successfully, but these errors were encountered: