On Fri, Mar 19, 2010 at 3:52 PM, William Stein <wst...@gmail.com> wrote:
> On Fri, Mar 19, 2010 at 12:47 AM, Dan Drake <dr...@kaist.edu> wrote: > > On Thu, 18 Mar 2010 at 09:05PM -0700, John H Palmieri wrote: > >> Sage uses non-standard command-line options (e.g., -notebook rather > >> than --notebook). I propose that we switch to standard ones. Here are > >> two reasons: > > > > A big +1 here. No need to reinvent the wheel; we are manually parsing > > command-line options, and should instead take advantage of the getopt or > > optparse modules. > > The main issue I see is that using getopt or optparse means that the > "local/bin/sage-sage" script will go from not depending on Python to > depending on Python. This may cause trouble for the build system, and > may slow down commands such as "sage -gp", since doing "sage -gp" now > means also starting Python, in addition to Pari. > > This code does the requisite parsing in pure shell script: http://code.google.com/p/shflags/, which I think removes the only negative :-) > Other than that, I can't see any negatives. > > The sage-sage file parsed like 2 or 3 options when I first wrote it, > and I planned to redo it "right", but then it kept getting longer... > > > Your implementation plan sounds good, and should let us shake out bugs > > without making Sage unusable for anyone. > > > >> By the way, while investigating this, I came up with some questions: > >> > >> - What should "sage blah.spkg" do? It looks like it's supposed to > >> install the spkg, although this isn't documented anywhere that I can > >> see. Should we keep this behavior, or just make the user type "sage -i > >> blah.spkg"? > > > > Off the top of my head, I think "sage blah.spkg" should ask you if you > > want to install the spkg and just exit if you say no. > > > >> - "sage -log" seems to be broken: it tries to write to the > >> nonexistent file SAGE_ROOT/changelog.txt. Should we remove it or fix > >> it? > > > > (Again off the top of my head...) I say remove this. It's doesn't seem > > relevant to our current development procedures. > > +1 > > > > >> - what is "sage -darcs" supposed to do? I don't know what "darcs" is, > >> and I don't see any packages which seem relevant. > > Delete it. > > >> > >> - what about "sage -axiom"? What package installs axiom? Fricas? > > Fricas. > > >> > >> - does anyone use "sage -crap"? "sage -min"? "sage -inotebook"? > > I use "sage -inotebook" and have used "sage -crap". I wrote "sage > -min" to satisfy complaints from David Harvey... > > >> - how about "sage -gthread" and friends? > > I don't know what that is. > > >> - how about "sage -valgrind" and friends, or "sage -t FILE -valgrind", > >> etc.? > > That should stay. And somebody should really be using it again :-). > > William > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com<sage-devel%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > > To unsubscribe from this group, send email to sage-devel+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > -- Tim Joseph Dumol <tim (at) timdumol (dot) com> http://timdumol.com -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
