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

Groups > comp.lang.python > #107099

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

Show key headers only | View raw

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/

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

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

csiph-web