#21: command line option parsing
---------------------------+------------------------------------------------
Reporter: was | Owner: mabshoff
Type: enhancement | Status: needs_review
Priority: critical | Milestone: sage-4.3.4
Component: interfaces | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Comment(by jhpalmieri):
Replying to [comment:10 jhpalmieri]:
> I've marked this as "needs review", but it might need work. In the
previously cited thread from sage-devel, there was the following
suggestion:
{{{
Another possibility might be to first check for "--gp", "--gap", etc.,
and do those before doing the general option parsing. I.e., just do
what you already planned, but with one optimization to deal with this
use case.
}}}
Okay, here's a new version which does this: it adds a file sage-sage-
quickstart which gets run first, implementing the above idea. Then if
SAGE_NEW_OPTIONS is nonempty, it calls sage-sage.py, the Python/optparse
version with GNU/Posix standard command-line options. Otherwise, it calls
the old parser sage-sage.
For the record, the commands in sage-sage-quickstart are: axiom, ecl/lisp,
gap, gp, hg, ipython, maxima, mwrank, python, R, singular. Are any others
particularly sensitive to startup times? (Using python adds something
less than .1 second on my two-year old iMac, so we're not talking about a
lot of time, in any case.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/21#comment:11>
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.
