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 Rogi
Recipients Rakeka, Rogi, eric.frederich, georg.brandl, mhammond, santoso.wijaya, vstinner
Date 2011-03-29.00:32:36
SpamBayes Score 4.312627e-05
Marked as misclassified No
Message-id <1301358758.97.0.653665333537.issue6498@psf.upfronthosting.co.za>
In-reply-to
Content
@mhammond

	After reading your post again I noticed you talk about
SystemError and not SystemExit. In fact, Py_Main() should not return on
SystemError. Teh documentation states "if the interpreter exits due to
an exception", which implies teh interpreter _exiting_, not simply
catching a exception.

	It is just a BAD IDEA to allow python functions to print
messages or call exit() as they wish. They should be split so teh
programmer could put printing and exiting where he finds appropriate.
Teh printing part is just another nuisance, but teh exit() is serious.

	Again, all of this could be accomplished while maintaining
backward compatibility.

Cheers.
History
Date User Action Args
2011-03-29 00:32:39Rogisetrecipients: + Rogi, mhammond, georg.brandl, vstinner, Rakeka, santoso.wijaya, eric.frederich
2011-03-29 00:32:38Rogisetmessageid: <1301358758.97.0.653665333537.issue6498@psf.upfronthosting.co.za>
2011-03-29 00:32:36Rogilinkissue6498 messages
2011-03-29 00:32:36Rogicreate