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


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

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

Started byBen Finney <ben+python@benfinney.id.au>
First post2016-04-17 06:24 +1000
Last post2016-04-17 06:24 +1000
Articles 1 — 1 participant

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 Ben Finney <ben+python@benfinney.id.au> - 2016-04-17 06:24 +1000

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

FromBen Finney <ben+python@benfinney.id.au>
Date2016-04-17 06:24 +1000
SubjectRe: sys.exit(1) vs raise SystemExit vs raise
Message-ID<mailman.62.1460838306.6324.python-list@python.org>
Dennis Lee Bieber <wlfraed@ix.netcom.com> writes:

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

That's fine; those values can be defined per operating system, and
maybe they should be.

My concern is that (according to the documentation) the “no error” exit
status *isn't even defined* on non-Unix operating systems, as though
no other OS uses it.

-- 
 \     “Do unto others twenty-five percent better than you expect them |
  `\      to do unto you. (The twenty-five percent is [to correct] for |
_o__)                            error.)” —Linus Pauling's Golden Rule |
Ben Finney

[toc] | [standalone]


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


csiph-web