There seem to be nothing special in ~/.ipython:
jscandal@jorges { ~/sw }$ ls /home/jscandal/.ipython/
Crash_report_ipython.txt history ipython_config_pylab.py
db history.json ipython_config_pysh.py
I have even moved ~/.ipython elsewhere, but sage will load the ipython from
my local directory, if it is available, and thus give the import error. It's
like if the path was hardcoded somewhere, but I don't see where. It's not in
the environment, as $ env | grep -i python returns nothing.
Wait! I think it's picking up ~/.local/bin/ipython, which has hardcoded the
location:
jscandal@jorges { ~/.local_disabled/bin }$ cat ipython
#!/usr/bin/python
# EASY-INSTALL-DEV-SCRIPT: 'ipython==0.11.dev','ipython'
__requires__ = 'ipython==0.11.dev'
from pkg_resources import require; require('ipython==0.11.dev')
del require
__file__ = '/home/jscandal/sw/ipython/ipython-git/IPython/scripts/ipython'
execfile(__file__)
I think that is what is going on. ~/.local/bin must be a standard place to
look for binaries? Is it expected to be like that? How does sage avoids, for
example, picking up on the system's python? Shouldn't it be the same here?
Well, at least I have an idea now, let's see if I can figure out a
workaround.
jorges
--
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-support
URL: http://www.sagemath.org