I suppose there is a bug in the sage bash script? =============== 101 102 # Return $out 103 echo "$out" 104 } ===============
should that be exit actually? On Saturday, 17 January 2015 19:28:22 UTC+1, Jernej Azarija wrote: > > Hello, > > I have to use Sage from an external comand and in order to do so I'll need > to rely on the exit status given by Sage. Considering a trivial example > > ============= > $ cat foo.sage > exit(0) > ============= > > > I get the following behaviour > > > ============= > $ sage la.sage > 0 > $ echo $? > 1 > ============= > > There are two things I am confused with here. > > 1. Why do we print 0? > > 2. Why is the exit status 1 - indicating an error by UNIX standards? > > > Is there any reason behind this? If yes , what would be the best way to > force my own exit status so that I can interpret the execution of Sage from > an external program? > > Best, > > Jernej > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
