-
Notifications
You must be signed in to change notification settings - Fork 31
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
install-maxima-jupyter sticks with lack of kernel. #58
Comments
It's not clear to me what is happening beyond the kernel failing to execute. Maybe |
Thank you for help |
Please try using the
|
If I am not mistaken, Sage builds Maxima with ECL. I don't know if Maxima-Jupyter can work with ECL. |
After a third trial the installation succeded. But now there is another problem (see file Connection failed.png). Robert |
@robert-dodier You are correct, the SageMath binary won't work. I forgot to update my intro text but used the path to the correct binary in my example. @roebix Please try |
It is fairly confusing task! |
It looks like the maxima script cannot find SBCL. You should probably make sure the sbcl binary is in |
Unfortunately it doesn't work with SBCL either. |
Your export command probably should have been export PATH=”$PATH:/Applications/Maxima.app/Contents/Resources/opt/bin” |
Unfortunately, the same problem is again apparent, there is no kernel. |
(I have copied the following from an email from Robert Moser.)
Dear Robert Dodier
install-maxima-jupyter sticks with lack of kernel.
What I did until now:
copy of maxima-jupyter-master on my MacBook Pro (macOS High Sierra).
Terminal: roberts-macbook-pro:maxima-jupyter-master roebi$ python3 ./install-maxima-jupyter.py --root=
pwd
Terminal: roberts-macbook-pro:maxima-jupyter-master roebi$ jupyter notebook
Jupiter launches correctly but maxima has no kernel. It seems to me that maxima uses python 2 instead of python 3.
Here I encose the relevant part of the protocol from terminal. Now I am exhausted - I would appreciate your help. Thank you.
Best regards
Robert Moser
20190530_2_Terminal.pdf
The text was updated successfully, but these errors were encountered: