Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

answered 2011-02-28 13:10:53 -0600

DSM gravatar image

Sage uses PYTHONPATH for its own purposes. If you add the directory to SAGE_PATH (export SAGE_PATH=/some/dir/here) it should work, at least it seems to for me.

Beware: it looks like SAGE_PATH is added before Sage's existing python in sage-env:

PYTHONPATH="$SAGE_PATH:$SAGE_ROOT/local/lib/python"   && export PYTHONPATH

so if you shadow one of the built-in modules you could get strange errors.

Sage uses PYTHONPATH for its own purposes. If you add the directory directory/directories to SAGE_PATH (export SAGE_PATH=/some/dir/here) it should work, at least it seems to for me.

Beware: it looks like SAGE_PATH is added before Sage's existing python in sage-env:

PYTHONPATH="$SAGE_PATH:$SAGE_ROOT/local/lib/python"   && export PYTHONPATH

so if you shadow one of the built-in modules you could get strange errors.

Sage uses PYTHONPATH for its own purposes. If you add the directory/directories to SAGE_PATH (export SAGE_PATH=/some/dir/here) it should work, at least it seems to for me.

Beware: it looks like SAGE_PATH is added before Sage's existing python in sage-env:

PYTHONPATH="$SAGE_PATH:$SAGE_ROOT/local/lib/python"   && export PYTHONPATH

so if you shadow one of the built-in modules you could get strange errors. [Not that you couldn't get errors if it were the other way 'round, of course, but you might not even be able to get to the prompt.]