Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-04-08 Thread Ondrej Certik
On Thu, Apr 8, 2010 at 9:07 PM, Robert Bradshaw wrote: > On Apr 8, 2010, at 8:59 PM, Ondrej Certik wrote: > >> On Fri, Mar 19, 2010 at 3:52 PM, John H Palmieri >> wrote: >>> >>> In the most recent patch, it does this: >>> >>> 1. The file SAGE_ROOT/sage calls the new shell script sage-sage- >>> qu

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-04-08 Thread Robert Bradshaw
On Apr 8, 2010, at 8:59 PM, Ondrej Certik wrote: On Fri, Mar 19, 2010 at 3:52 PM, John H Palmieri > wrote: In the most recent patch, it does this: 1. The file SAGE_ROOT/sage calls the new shell script sage-sage- quickstart, which runs sage-env and then checks for --gp, --hg, etc. 2. If it fin

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-04-08 Thread Ondrej Certik
On Fri, Mar 19, 2010 at 3:52 PM, John H Palmieri wrote: > > > On Mar 19, 2:29 pm, William Stein wrote: >> On Fri, Mar 19, 2010 at 2:25 PM, John H Palmieri >> wrote: >> >> >> >> >> >> >> >> > On Mar 19, 11:13 am, Robert Bradshaw >> > wrote: >> >> On Mar 19, 2010, at 10:23 AM, Nick Alexander wro

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 2:29 pm, William Stein wrote: > On Fri, Mar 19, 2010 at 2:25 PM, John H Palmieri > wrote: > > > > > > > > > On Mar 19, 11:13 am, Robert Bradshaw > > wrote: > >> On Mar 19, 2010, at 10:23 AM, Nick Alexander wrote: > > >> > On 19-Mar-10, at 6:53 AM, Jason Grout wrote: > > >> >> On 03

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 11:06 am, William Stein wrote: > On Fri, Mar 19, 2010 at 9:00 AM, John H Palmieri > wrote: > > 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 optimi

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread William Stein
On Fri, Mar 19, 2010 at 2:25 PM, John H Palmieri wrote: > > > On Mar 19, 11:13 am, Robert Bradshaw > wrote: >> On Mar 19, 2010, at 10:23 AM, Nick Alexander wrote: >> >> >> >> >> >> >> >> > On 19-Mar-10, at 6:53 AM, Jason Grout wrote: >> >> >> On 03/18/2010 10:05 PM, John H Palmieri wrote: >> >>>

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 11:13 am, Robert Bradshaw wrote: > On Mar 19, 2010, at 10:23 AM, Nick Alexander wrote: > > > > > > > > > On 19-Mar-10, at 6:53 AM, Jason Grout wrote: > > >> On 03/18/2010 10:05 PM, John H Palmieri wrote: > >>> Sage uses non-standard command-line options (e.g., -notebook rather > >>> t

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 11:06 am, William Stein wrote: > > I'm still concerned about slowing down all of the "sage > -various_system" commands.  A typical use case of Sage for some > sysadmins is to install Sage system-wide, type "sage: > install_scripts('/usr/local/bin/')", and get scripts "gp", "gap", > etc.

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread Robert Bradshaw
On Mar 19, 2010, at 11:06 AM, William Stein wrote: On Fri, Mar 19, 2010 at 9:00 AM, John H Palmieri > wrote: On Mar 19, 1:36 am, William Stein wrote: On Fri, Mar 19, 2010 at 1:31 AM, Dan Drake wrote: On Fri, 19 Mar 2010 at 12:52AM -0700, William Stein wrote: The main issue I see is that usin

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread Robert Bradshaw
On Mar 19, 2010, at 10:23 AM, Nick Alexander wrote: On 19-Mar-10, at 6:53 AM, Jason Grout wrote: On 03/18/2010 10:05 PM, 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 rea

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread William Stein
On Fri, Mar 19, 2010 at 9:00 AM, John H Palmieri wrote: > On Mar 19, 1:36 am, William Stein wrote: >> On Fri, Mar 19, 2010 at 1:31 AM, Dan Drake wrote: >> > On Fri, 19 Mar 2010 at 12:52AM -0700, William Stein wrote: >> >> The main issue I see is that using getopt or optparse means that the >> >>

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread Nick Alexander
On 19-Mar-10, at 6:53 AM, Jason Grout wrote: On 03/18/2010 10:05 PM, 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: +1! When this issue came up a year or two ago,

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 6:52 am, Martin Albrecht wrote: > > - how about "sage -valgrind" and friends, or "sage -t FILE -valgrind", > > I find these incredibly useful! Great! I thought someone had said that they were broken, so I'm happy that they're not. -- John -- To post to this group, send an email to

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread John H Palmieri
On Mar 19, 1:36 am, William Stein wrote: > On Fri, Mar 19, 2010 at 1:31 AM, Dan Drake wrote: > > On Fri, 19 Mar 2010 at 12:52AM -0700, William Stein wrote: > >> 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 Pyt

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread Jason Grout
On 03/18/2010 10:05 PM, 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: +1! When this issue came up a year or two ago, there seemed to be a surprising amount of oppos

Re: [sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread William Stein
On Fri, Mar 19, 2010 at 12:54 AM, Adam Webb wrote: > > > On Mar 19, 5:05 am, 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: >> >> 1. They're standard, and standa

[sage-devel] Re: proposal: standard command-line options in Sage

2010-03-19 Thread Adam Webb
On Mar 19, 5:05 am, 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: > > 1. They're standard, and standards are good. People used to Unix-type > systems will expect