#11914: `sage -n` fails when current directory is $SAGE_ROOT/devel/sage
-----------------------+----------------------------------------------------
Reporter: kini | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-4.7.2
Component: scripts | Keywords: startup, crash, sage-env
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-----------------------+----------------------------------------------------
Comment(by ppurka):
Replying to [comment:13 leif]:
> (I don't know what potentially weird shells might source `sage-env`,
otherwise I'd use `export FOO="bar"` or `export FOO BAR` etc.)
Is sage-env even called from anywhere outside Sage scripts? It seems weird
that all the sage scripts are called as `#!/usr/bin/env bash` but the
scripts themselves are not written (most of the time) as bash scripts. It
should probably be like the `$SAGE_ROOT/sage` script should be POSIX shell
compatible and then the rest should be proper bash scripts, since they
anyway invoke bash. It will make the scripts nicer and easier to read.
Thanks for the PYTHONPATH fix. Didn't know that empty paths resolve to
current directory.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11914#comment:16>
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.
