You may be right, I did have ~/.local/bin added to my path. However,
removing any reference to it (in .bashrc, where it was aded in the first
place) still confuses sage:
jscandal@jorges { ~ }$ env | grep PATH
DEFAULTS_PATH=/usr/share/gconf/gnome.default.path
PATH=/home/jscandal/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
MANDATORY_PATH=/usr/share/gconf/gnome.mandatory.path
WINDOWPATH=7
jscandal@jorges { ~ }$ cd sw/sage/sage-4.6.1/
jscandal@jorges { ~/sw/sage/sage-4.6.1 }$ ./sage
----------------------------------------------------------------------
| Sage Version 4.6.1, Release Date: 2011-01-11 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/jscandal/sw/sage/sage-4.6.1/local/bin/sage-ipython", line 19,
in <module>
from IPython.CrashHandler import CrashHandler
ImportError: No module named CrashHandler
So, it might not be a standard directory, but it must be cached somewhere.
But my point is that this behavior seems to be wrong, because if the same
applied, for example, to python, then sage would be using the system python
instead of its own version. What's the difference w/ ipython? Shouldn't sage
prepend the PATH variable with its own locations? Is there a place where
this behavior is defined? I must admit that I still struggle a bit to find
my way in the sage docs
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
