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 underrun
Recipients underrun
Date 2013-12-18.16:10:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387383015.85.0.019158387414.issue20016@psf.upfronthosting.co.za>
In-reply-to
Content
calling exit() or quit() is actually very cumbersome especially as most other commandline tools that have a command interface allow you to exit or quit by typing exit or quit and not by calling a function.

if quitter's builtins are only available in the interactive interpreter this seems like it would be perfectly safe. now that we are looking at 3.x going forward, perhaps we can reopen this: http://bugs.python.org/issue8220
History
Date User Action Args
2013-12-18 16:10:15underrunsetrecipients: + underrun
2013-12-18 16:10:15underrunsetmessageid: <1387383015.85.0.019158387414.issue20016@psf.upfronthosting.co.za>
2013-12-18 16:10:15underrunlinkissue20016 messages
2013-12-18 16:10:15underruncreate