Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #107099 > unrolled thread

Re: sys.exit(1) vs raise SystemExit vs raise

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: sys.exit(1) vs raise SystemExit vs raise Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-04-16 12:09 -0400
    Re: sys.exit(1) vs raise SystemExit vs raise Steven D'Aprano <steve@pearwood.info> - 2016-04-17 11:17 +1000

#107099 — Re: sys.exit(1) vs raise SystemExit vs raise

On Sat, 16 Apr 2016 16:56:10 +1000, Ben Finney <ben+python@benfinney.id.au>
declaimed the following:

>Stephen Hansen <me@ixokai.io> writes:
>
>> > * You can use named constants from ‘os’ for the purpose of specifying
>> >   exit status numbers.
>>
>> Only on *nix.
>
>Hmm, I didn't see that. It seems strange that even the constant for “no
>error” exit status should be defined only for Unix :-/
>
	VMS had a whole slew of "no error" status values (essentially all
positive odd integers were "success", but different values carried
additional information. Even integers were errors [I forget if positive or
negative were "warnings" vs "error"])

	True, the simplest was "1", which just carried "success -- no
additional details" and "0" was "unspecified failure".
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/

[toc] | [next] | [standalone]

#107146

On Sun, 17 Apr 2016 02:09 am, Dennis Lee Bieber wrote:


> VMS had a whole slew of "no error" status values (essentially all
> positive odd integers were "success", but different values carried
> additional information. 

1 = success
3 = success against all odds
5 = success but at great cost
7 = success, and it was as easy as falling off a log
9 = success, and it was so easy you ought to be ashamed for
    asking the computer to do it instead of doing it yourself
11 = I told you I already did it yesterday
13 = done, but it wasn't worth doing
15 = well that was easier than I expected
17 = that was harder than I expected
19 = I did it, but I'm not going to do it again

> Even integers were errors [I forget if positive or 
> negative were "warnings" vs "error"])
> 
> True, the simplest was "1", which just carried "success -- no
> additional details" and "0" was "unspecified failure".



-- 
Steven

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web