#12627: The sage-sage script engraves paths to executables
-------------------------------+--------------------------------------------
   Reporter:  Snark            |          Owner:  leif           
       Type:  defect           |         Status:  positive_review
   Priority:  major            |      Milestone:  sage-5.0       
  Component:  scripts          |       Keywords:  rd2            
Work_issues:                   |       Upstream:  N/A            
   Reviewer:  R. Andrew Ohana  |         Author:  Julien Puydt   
     Merged:                   |   Dependencies:                 
-------------------------------+--------------------------------------------

Comment(by leif):

 Julien, I'm not sure whether you're aware of that, but your patch changes
 in at least ''some'' situations the ''fully intentional'' behavior.

 For example, a couple of Sage components / programs are ''optional'', like
 e.g. `kash` or `Macaulay2`, and it is '''not''' intended to run a system-
 wide / non-Sage version of `kash` (that might be found along `PATH`) if
 one types `sage --kash`.  (Although I admit that the current response in
 case Sage's version ''isn't'' installed -- ''"File not found"'' -- is
 quite odd, i.e., not very user-friendly.)

 In other cases a path is prepended ''to make sure'' we really run the
 correct instance of a Sage script, namely that of the ''"current"'' Sage
 installation, given by `SAGE_ROOT` (or `SAGE_LOCAL`), or to make sure our
 assumptions about the current directory (or other variable settings) are
 correct -- especially since different people develop things, sometimes
 perhaps too independently.  Not very pythonic, but similar to `assert()`,
 which at least ''signals'' errors [before things get worse and
 untraceable].

 Redundancy is ''necessary'' to achieve some robustness, catch (and
 hopefully appropriately handle) errors when they occur, or as early as
 possible, e.g. if a script or program doesn't exist where it is supposed
 to be located, since we cannot rule out an installation gets messed up --
 probably by Sage itself, due to bugs, if not by a user...

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12627#comment:7>
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.

Reply via email to