[Python-Dev] a quit that actually quits (original) (raw)
Samuele Pedroni pedronis at strakt.com
Wed Dec 28 12:57:29 CET 2005
- Previous message: [Python-Dev] a quit that actually quits
- Next message: [Python-Dev] a quit that actually quits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michael Hudson wrote:
skip at pobox.com writes:
Fredrik> a quit/exit command that actually quits, instead of printing a Fredrik> "you didn't say please!" message. I like Fredrik's idea more and more. The thing that bothers me about it is that the standard way you tell python to do something is "call a function" -- to me, a special case for exiting the interpreter seems out of proportion.
also worth remarking is that is quite a FAQ at least for Jython, how to convince python to accept bare words (plus args) as function calls. So this magic is confusing and in the wrong direction from that point of view, given that we don't plan to support that at all.
In other news, clever hacks with tbnext and so on also seem excessive. Why not have the equivalent of "if input.rstrip() == 'exit': sys.exit()" in the implementation of the interactive interpreter?
Cheers, mwh
- Previous message: [Python-Dev] a quit that actually quits
- Next message: [Python-Dev] a quit that actually quits
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]