Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #107082
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Newsgroups | comp.lang.python |
| Subject | Re: sys.exit(1) vs raise SystemExit vs raise |
| Date | 2016-04-16 16:56 +1000 |
| Message-ID | <mailman.41.1460790007.6324.python-list@python.org> (permalink) |
| References | <CACT3xuUFeOXbjwiWhgZ90UMPi5xXQaj9HpxU3Aepz2Hr8Kw42Q@mail.gmail.com> <20160416034833.GA24653@cskk.homeip.net> <858u0ew5qg.fsf@benfinney.id.au> <1460784872.1843058.580428001.63445E11@webmail.messagingengine.com> <85zisuujn9.fsf@benfinney.id.au> |
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 comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: sys.exit(1) vs raise SystemExit vs raise Ben Finney <ben+python@benfinney.id.au> - 2016-04-16 16:56 +1000
csiph-web