Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #107084 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2016-04-16 17:08 +1000 |
| Last post | 2016-04-16 17:08 +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 Chris Angelico <rosuav@gmail.com> - 2016-04-16 17:08 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2016-04-16 17:08 +1000 |
| Subject | Re: sys.exit(1) vs raise SystemExit vs raise |
| Message-ID | <mailman.42.1460790525.6324.python-list@python.org> |
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 top | Article view | comp.lang.python
csiph-web