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

From	Dennis Lee Bieber <wlfraed@ix.netcom.com>
Newsgroups	comp.lang.python
Subject	Re: sys.exit(1) vs raise SystemExit vs raise
Date	2016-04-16 12:09 -0400
Organization	IISS Elusive Unicorn
Message-ID	<mailman.52.1460822977.6324.python-list@python.org> (permalink)
References	(1 earlier) <20160416034833.GA24653@cskk.homeip.net> <858u0ew5qg.fsf@benfinney.id.au> <1460784872.1843058.580428001.63445E11@webmail.messagingengine.com> <85zisuujn9.fsf@benfinney.id.au> <lno4hb1hpnqfqfmt1cq0r8gmhm4fmq1ajf@4ax.com>

Show all headers | 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