#11460: upgrade ipython to 0.10.2
------------------------+---------------------------------------------------
Reporter: jason | Owner: tbd
Type: task | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: packages | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
------------------------+---------------------------------------------------
Comment(by jhpalmieri):
It looks as though we still need the patch. With your spkg, I get this
message when running `sage -gdb` on my OS X box:
{{{
. done
Reading symbols for shared libraries warning: Could not find object file
"/Applications/sage_builds/11460/sage-4.7.1/spkg/build/python-2.6.4.p11/src/build/temp.macosx-10.6-i386-2.6/Applications/sage_builds/11460/sage-4.7.1/spkg/build/python-2.6.4.p11/src/Modules/_hashopenssl.o"
- no debug information available for
"/Applications/sage_builds/11460/sage-4.7.1/spkg/build/python-2.6.4.p11/src/Modules/_hashopenssl.c".
.... done
Traceback (most recent call last):
File "/Applications/sage_builds/11460/sage-4.7.1/local/bin/sage-
ipython", line 18, in <module>
import IPython
File "/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6
/site-packages/IPython/__init__.py", line 58, in <module>
__import__(name,glob,loc,[])
File "/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6
/site-packages/IPython/ipstruct.py", line 17, in <module>
from IPython.genutils import list2dict2
File "/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6
/site-packages/IPython/genutils.py", line 114, in <module>
import IPython.rlineimpl as readline
File "/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6
/site-packages/IPython/rlineimpl.py", line 49, in <module>
if status == 0 and len(result) > 0:
NameError: name 'status' is not defined
>>>
}}}
With a version including the patch, it gets past this point; instead, it
ends up like this:
{{{
---------------------------------------------------------------------------
RuntimeError Traceback (most recent call
last)
/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6/site-
packages/IPython/ipmaker.pyc in force_import(modname, force_reload)
61 reload(sys.modules[modname])
62 else:
---> 63 __import__(modname)
64
65
/Applications/sage_builds/11460/sage-4.7.1/ipy_profile_sage.py in
<module>()
14 from sage.misc.interpreter import attached_files
15
---> 16 branch =
sage.misc.misc.branch_current_hg_notice(sage.misc.misc.branch_current_hg())
17 if branch:
18 print branch
/Applications/sage_builds/11460/sage-4.7.1/local/lib/python2.6/site-
packages/sage/misc/misc.pyc in branch_current_hg()
2051 i = s.rfind('->')
2052 if i == -1:
-> 2053 raise RuntimeError, "unable to determine branch?!"
2054 s = s[i+2:]
2055 i = s.find('-')
RuntimeError: unable to determine branch?!
Error importing ipy_profile_sage - perhaps you should run %upgrade?
WARNING: Loading of ipy_profile_sage failed.
}}}
Two comments:
- This also doesn't look great, but it's exactly the same behavior as
with IPython 0.9.
- With the patched version, at least once I've been able to run `sage
-gdb` without any errors at all.
So I think the patch should be there, at least to maintain the status quo.
I'm posting a link to a new spkg, based on yours, which reinstates the
patch. I'm attaching the hg patch for the Mercurial repo for the spkg, so
you can see what's been changed. I'm also posting logs of what happens
when you run `sage -gdb` with the current 0.9.1.p0 spkg, with your 0.10.2
spkg, and with my 0.10.2.p0 spkg. (Notice how much longer the logs are
for spkgs which use the patch: they seem to process many more libraries.
The logs for 0.9.1.p0 and 0.10.2.p0 are identical, except for the paths
involved.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11460#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.