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


Groups > comp.lang.python > #107084

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

From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Subject Re: sys.exit(1) vs raise SystemExit vs raise
Date 2016-04-16 17:08 +1000
Message-ID <mailman.42.1460790525.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> <CAPTjJmobZgyEAiqLqTr5avfxWsX6S4EFyOYRUx6f+QjzVT3XGQ@mail.gmail.com>

Show all headers | View raw


On Sat, Apr 16, 2016 at 4:56 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
> 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 :-/

Maybe it's an error to use anything non-Unix??

ChrisA

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


Thread

Re: sys.exit(1) vs raise SystemExit vs raise Chris Angelico <rosuav@gmail.com> - 2016-04-16 17:08 +1000

csiph-web