Control: affects -1 cantor-backend-sage Control: summary -1 SAGE_ROOT unset + sage-env removal inhibits Cantor backend
On Friday, October 16, 2020 11:29:14 AM EDT Jan Kriho wrote: > The launcher scripts is dependent on sage-env binary which sets env for > executing further commands Note that even if sage-env were to be available, I don't think Cantor would be able to find it. It appears to invoke `sage --root` to figure out where to look, but the output is empty. Also with sage --sh: > sage --sh > > Starting subshell with Sage environment variables set. Don't forget to exit > when you are done. Beware: > * Do not do anything with other copies of Sage on your system. > * Do not use this for installing Sage packages using "sage -i" or for > running "make" at Sage's root directory. These should be done > outside the Sage shell. > > Bypassing shell configuration files... > > Note: SAGE_ROOT= Cantor could be doing things in a more clean way regardless though. Instead of fiddling with $SAGE_ROOT in a shell script, it could use the one-liner sage --ipython3 -i --simple-prompt or use /usr/bin/sage --sh for the shebang in the script and call sage-ipython
signature.asc
Description: This is a digitally signed message part.