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 mhammond
Recipients Rakeka, Rogi, georg.brandl, mhammond, vstinner
Date 2011-03-28.07:02:42
SpamBayes Score 1.1456947e-12
Marked as misclassified No
Message-id <1301295762.78.0.827066150592.issue6498@psf.upfronthosting.co.za>
In-reply-to
Content
Note the quoted documentation in comment 1, the paragraph "Note that if an otherwise unhandled SystemError ..."

I don't think that paragraph is correct - SystemError doesn't seem to terminate Py_Main - but if you replace "SystemError" with "SystemExit", that paragraph is correct, including the comment about Py_InspectFlag.

So I think there are 2 simple documentation bugs (the component of this bug is "Documentation") and not necessarily a behaviour bug (even though the "type" is set to behaviour :)

* The first paragraph should have references to sys.exit() removed (I didn't mention this in my previous comment!)

* The second paragraph should s/SystemError/SystemExit/ and optionally a note that calling sys.exit() will result in a SystemExit exception.

I just traced through this in Python 2.6 - PyRun_InteractiveOneFlags winds up calling PyErr_PrintEx() and this function explicitly checks for SystemExit and calls handle_system_exit, which calls exit().  There doesn't seem to be any special handling for SystemError at all.
History
Date User Action Args
2011-03-28 07:02:42mhammondsetrecipients: + mhammond, georg.brandl, vstinner, Rogi, Rakeka
2011-03-28 07:02:42mhammondsetmessageid: <1301295762.78.0.827066150592.issue6498@psf.upfronthosting.co.za>
2011-03-28 07:02:42mhammondlinkissue6498 messages
2011-03-28 07:02:42mhammondcreate