-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[RFC] New package: sagelib-9.5 #35339
Conversation
Let me first say you've done a great job. |
For some reason, I struggle to pick up this kernel in jupyterlab.
which also matches what we were doing previosuly, as well as suggested by sage docs |
I only added stuff that is needed to pass doctests. There is some functionality to cython-compile code (e.g. you may want to define a function in cython inside a notebook) and that needs at least headers and sometimes libraries, and a working gcc (which is required indirectly via gcc-fortran). It might be possible to add "features" to sage that correspond to presence of gcc and headers, etc. but I'm not sure this is worth the trouble. Although some sage developers are trying to move it in a "modularization" direction such that it's possible to split it in parts and in that sense it could make sense to split out a "sagemath-cython" subpkg that gives this ability, etc. |
The jupyter kernel spec is fixed right at the top of the
The goal is for the notebook to work out of the box. How are you running it? I'm just doing
and the browser is launched with a jupyter session in which I can create a new "SageMath 9.5" notebook. It is identical if run as Are you sure you don't have leftover cruft from "fixing" of jupyter for the other package? You shouldn't have anything at all in |
I removed
although I may have some leftovers here
only thing is it complais about many |
As for tests:
This is just because
This seems to be just the error bound for the integral (the value seems to be exactly the same, more than 4e-11 close in any case), so not a real issue safe and should be easy to fix and upstream. I am guessing the reason we didn't see this before is that in the other package we are running I expect two small patches will make everything pass. If we figure out the issues @dkwo is having with the notebook (which works fine for me), I think we'd have something ready to merge. @leahneukirchen: can you test in your webapp? |
If I remove sagelib and jupyterlab, and by hand
(probably again leftovers), then reinstall them, I'm on the same page as you, so this is an issue with jupyterlab, not sagelib. |
Works as a jupyter notebook without any adjustments. I updated |
I pushed the fix for the two doctest failures. If everything works ok I plan on redoing this PR later today as a package named |
And then we can merge it right? :) |
I moved back to the |
This is a different approach for a sagemath package than #34030.
Here we build the sagelib as a python module and install it in the system site-packages. The scripts are all installed in
/usr/lib/sagemath/bin
to avoid polluting the PATH. A symlink/usr/bin/sagelib
is provided.NOTE: for the moment this is set up so it can coexists together with the
sagemath
package; that's why the package name issagelib
(instead ofsagemath
) and the binary issagelib
(instead ofsage
). The plan is to rename this package tosagemath
and the binary tosage
to replace the other since this one is much simpler and should work better.With this version jupyter notebook should work out of the box without any adjustments. Please let me know if there's anything missing.
Any comments about packaging, package layout, etc, now is the moment. I would like to get this merged soon since everything seems to be in place.
Cc: @dkwo @leahneukirchen