Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #107082 > unrolled thread
| Started by | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| First post | 2016-04-16 16:56 +1000 |
| Last post | 2016-04-16 16:56 +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.
Re: sys.exit(1) vs raise SystemExit vs raise Ben Finney <ben+python@benfinney.id.au> - 2016-04-16 16:56 +1000
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2016-04-16 16:56 +1000 |
| Subject | Re: sys.exit(1) vs raise SystemExit vs raise |
| Message-ID | <mailman.41.1460790007.6324.python-list@python.org> |
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 :-/ -- \ “Geeks like to think that they can ignore politics. You can | `\ leave politics alone, but politics won't leave you alone.” | _o__) —Richard M. Stallman, 2002-07-26 | Ben Finney
Back to top | Article view | comp.lang.python
csiph-web