Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread Jeroen Demeyer
On 2015-01-30 05:28, William Stein wrote: I'm just thinking it's a little depressing that we somehow broke Sage this way... We should really switch to the proper argument parsing code that John Palmieri wrote (like 4 years ago). I guess you refer to http://trac.sagemath.org/ticket/21 -- You

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread William Stein
On Thu, Jan 29, 2015 at 8:29 PM, Francois Bissey wrote: > Should be solved in rc0 this is Trac #17685. I have been plagued by this for > a while because my machine name is qcd-nzi3 - notice it contains "-n". > Your script similarly has "-n" in it. Automatic fail. Look at the code there: -if [[ "

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread Rob Beezer
Thanks very much, François. I'll watch that ticket. On Thursday, January 29, 2015 at 8:29:16 PM UTC-8, François wrote: > > Should be solved in rc0 this is Trac #17685. I have been plagued by this > for > a while because my machine name is qcd-nzi3 - notice it contains “-n”. > Your script simil

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread William Stein
On Thu, Jan 29, 2015 at 8:26 PM, Rob Beezer wrote: > Genius. All three failing scripts have "-n" in the filename, and the > renaming to "a.sage" allows the file to succeed. And the rest that do > succeed do not have a "-n." I'm just thinking it's a little depressing that we somehow broke Sage t

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread Francois Bissey
Should be solved in rc0 this is Trac #17685. I have been plagued by this for a while because my machine name is qcd-nzi3 - notice it contains “-n”. Your script similarly has “-n” in it. Automatic fail. François > On 30/01/2015, at 17:12, Rob Beezer wrote: > > I have a short chunk of Sage code t

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread Rob Beezer
Genius. All three failing scripts have "-n" in the filename, and the renaming to "a.sage" allows the file to succeed. And the rest that do succeed do not have a "-n." I'll make a ticket soon unless I hear that this is known already. Thanks, William! Rob On Thursday, January 29, 2015 at 8:15

Re: [sage-devel] Sage script at command-line fails in a suspicious way

2015-01-29 Thread William Stein
On Thu, Jan 29, 2015 at 8:12 PM, Rob Beezer wrote: > I have a short chunk of Sage code that I am running from the command line. > It produces errors with newer versions of Sage, but works as intended with > older versions (producing a graphics file). Of about 20 such chunks, 3 > appear to be fail