I am attempting to follow the instructions here to install Sage Cell Server
2 on Sage 5.4-rc1: https://github.com/sagemath/sagecell/issues/344

Here is my complete list of commands on a fresh install of Ubuntu 12.10 x64
(I'm having the identical problem on a second machine with an old install
of Ubuntu 12.04 x64):

*sudo apt-get install build-essential m4 gfortran perl dpkg-dev make tar
dvipng ffmpeg imagemagick openssh-client texlive texlive-latex-extra xpdf
xdvi libssl-dev libssl0.9.8 tk8.5-dev tk8.5-doc bzr git mercurial uuid-dev
python ipython*
*cp sage-5.4.rc1.tar /opt/sage/
*
*cd /opt/sage/
*
*tar -xvf sage-5.4.rc1.tar
*
*cd sage-5.4.rc1/*
*export MAKE="make -j4"
*
*make*

# from Sage Trac #12719 (http://trac.sagemath.org/sage_trac/ticket/12719):

*./sage --hg qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719_ROOT_configuration_files.patch
./sage --hg qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-ipythondir013.patch
./sage --hg -R local/bin qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-scripts.patch
./sage --hg -R local/bin qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719_remove_sage_gdb_ipython.patch
./sage --hg -R local/bin qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-test-displayhook.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-5.1beta1.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-move_to_preparser_rebased.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719_ipython_fixes.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719_dedent.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-crash.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-cellmagics013.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-newipython-take2.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-displayhook.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-fix-transformer.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-5.4rc1.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-remove-plugin.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/12719-displayhook-library.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-pager.patch
./sage --hg -R devel/sage qimport -P
http://trac.sagemath.org/sage_trac/raw-attachment/ticket/12719/trac_12719-preparse-doctest.patch
./sage -i http://sage.math.washington.edu/home/jason/ipython-0.13.1.spkg*
*./sage -br*

This last step fails. and spits out Sage_crash_report.txt:
http://pastebin.com/Qy2f7UPd
The crash traceback states: "KeyError  Python 2.7.3:
/opt/sage/sage-5.4.rc1/local/bin/python"

from *./sage -advanced* I see that the '-br' flag is supposed to build and
run the selected Sage branch.
If I just use *./sage -b* instead, it completes successfully, but crashes
with the error above when I try to run Sage.
If I ignore this and continue the Sage Cell 2 installation instructions...

*./sage -sh -c "easy_install
https://github.com/ipython/ipython/zipball/master"*
# appears to successfully install ipython 0.14.dev; if *./sage -br* is run,
still crashes

*./sage -i
http://sage.math.washington.edu/home/jason/sagecell-spkg/sagecell-2012-09-25.spkg
*
# appears to successfully install the Sage Cell 2 spkg; *./sage -br* still
crashes

*cd devel/sagecell
cp config_default.py config.py
nano config.py*
# change sage, host, and username variables to allow passwordless localhost
SSH'ing

*../../sage -sh -c "make -B"*
# appears to complete successfully

*../../sage web_server.py*
# the Sage Cell Server page can now be visited at localhost:8888

basic algebra works, but if I try to plot something or use any advanced
functionality I get 'Internal Python errors': http://pastebin.com/phirVuKF
I have over 5GB of free memory on this machine.

I figure this must have something to do with my Python install, maybe
because I have python and ipython installed globally.  I tried some
alternative ipython installation instructions:

*cd ~/repo
git clone git://github.com/ipython/ipython.git
cd ipython
/opt/sage/sage-5.4.rc1/sage setup.py install*
# completes successfully, but sage still crashes and the contents of
Sage_crash_report.txt remain the same

I tried to force a reinstall of Sage's internal version of Python:
*./sage -f python*
*./sage -b*
# completes successfully; same crash still occurs

After failing to get this working, I installed sage-5.3 (no patches, no
SageCell, etc) on this system and it functions perfectly.
Any help toward getting Sage Cell Server to work would be much appreciated!
 If I'm better off using sage-5.4.rc2 or sage-5.3, just let me know - I was
using sage-5.4.rc1 since that's what the install documentation suggested.

  Brandon Curtis, PhD Candidate
UC Berkeley - Chem/Bio Eng <http://www.linkedin.com/in/brandoncurtis>
<https://kindle.amazon.com/profile/Brandon-Curtis/5046185>
  <https://plus.google.com/u/0/105858766264293200612/about>
<http://brandoncurtis.net>
  <http://jbei.org>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To post to this group, send email to sage-support@googlegroups.com.
To unsubscribe from this group, send email to 
sage-support+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support?hl=en.


Reply via email to