This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients Arfrever, David.Manowitz, docs@python, ggenellina, jgehrcke, martin.panter, pitrou, stutzbach, terry.reedy
Date 2015-02-10.01:20:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423531233.59.0.515976430005.issue6634@psf.upfronthosting.co.za>
In-reply-to
Content
If it were me, I’d drop the Notes and Warnings (never been a fan), and put Thing #2 first, and then Thing #1. Maybe something like

'''
sys.exit([arg])

Exit from Python. . . . and it is possible to intercept the exit attempt at an outer level. When called from a thread other than the main thread, this causes the thread to exit silently instead, and is equivalent to calling :func:`thread.exit`.

The optional argument *arg* can be an integer giving the exit status (defaulting to zero). Passing ``None`` is equivalent to passing zero. Any other object is printed to `stderr` and results in an exit status of 1. In
particular, ``sys.exit("some error message")`` is a quick way to exit a
program when an error occurs. When called from a thread other than the main thread, nothing is printed and the argument is ignored.

An exit status of zero is considered “successful termination” and any nonzero status is considered “abnormal termination” . . . Unix programs generally use 2 for command line syntax errors and 1 for all other kinds of errors.
'''
History
Date User Action Args
2015-02-10 01:20:34martin.pantersetrecipients: + martin.panter, terry.reedy, ggenellina, pitrou, stutzbach, Arfrever, jgehrcke, docs@python, David.Manowitz
2015-02-10 01:20:33martin.pantersetmessageid: <1423531233.59.0.515976430005.issue6634@psf.upfronthosting.co.za>
2015-02-10 01:20:33martin.panterlinkissue6634 messages
2015-02-10 01:20:31martin.pantercreate