#12627: The sage-sage script engraves paths to executables
-----------------------+----------------------------------------------------
Reporter: Snark | Owner: leif
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: scripts | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
-----------------------+----------------------------------------------------
Comment(by Snark):
With the current situation, sage-env makes sure the rest of sage has a
good environment to work, but sage-sage decides it knows better and
shortcuts it.
This is one of the situations I denounced on the sage-devel mailing-list,
where sage is supposed to be modular but in fact isn't, because the
modules don't just depend on each other's work : there are hidden, subtle
places where they do their own thing.
I have a few patches up my sleeve to move things around ; they're not
supposed to go upstream anytime soon. But they make some hidden things
appear, so I fix them, and as it's interesting for upstream, I report
immediately, with a proper fix, independent of my experiments.
To be fully honest, the goal of my not-for-upstream experiments is
precisely to find modularity problems and fix them...
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12627#comment:5>
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.
