#21: command line option parsing
-------------------------------+--------------------------------------------
       Reporter:  was          |         Owner:  jdemeyer  
           Type:  enhancement  |        Status:  needs_work
       Priority:  critical     |     Milestone:  sage-6.0  
      Component:  interfaces   |    Resolution:            
       Keywords:               |   Work issues:            
Report Upstream:  N/A          |     Reviewers:            
        Authors:               |     Merged in:            
   Dependencies:  #9958        |      Stopgaps:            
-------------------------------+--------------------------------------------

Comment (by rohana):

 Replying to [comment:42 jdemeyer]:
 > But what about `sage-env` then?  That's needed by `sage-sh`, so it
 cannot be Python-based.
 Definitely short term I don't think it is realistic to make the entire
 startup entirely python because we don't have any python module to setup a
 suitable environment, however I think it would be good to still make
 separate out sage-sh:

 Specifically I would have the root level sage script be (more or less)

 {{{
 #!/usr/bin/env sh

 "$0-sh" -c "sage $*"
 }}}

 and have `SAGE_LOCAL/bin/sage` be a pure python script.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/21#comment:43>
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].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to