[ python-Bugs-1173637 ] quit should quit
SourceForge.net
noreply at sourceforge.net
Fri Apr 1 06:35:18 CEST 2005
Bugs item #1173637, was opened at 2005-03-30 13:37
Message generated for change (Comment added) made by isandler
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1173637&group_id=5470
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Matt Chaput (mchaput)
Assigned to: Nobody/Anonymous (nobody)
Summary: quit should quit
Initial Comment:
When the user types "quit" in the interpreter, instead
of quitting the program gives him or her a lecture on
the "proper" way to quit.
This is very obnoxious.
Since the interpreter obviously understands the "quit"
command, it should just quit, dammit.
----------------------------------------------------------------------
Comment By: Ilya Sandler (isandler)
Date: 2005-03-31 20:35
Message:
Logged In: YES
user_id=971153
I am not sure adding quit to interpreter is such a good idea:
Right now quit is treated as an ordinary (non-keyword)
identifier...
(with a bit of magic: if quit is not defined then lecture
the user :-))...
E.g now you can do this:
>>> quit=2
>>> quit
2
Would you want to disallow this usage when quit becomes a
"magic word"?
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2005-03-31 01:49
Message:
Logged In: YES
user_id=6656
I'm not so sure typing quit should quit -- that doesn't seem like Python to
me (how would you implement it?)
Having quit be the same object as sys.exit seems sensible.
----------------------------------------------------------------------
Comment By: Raymond Hettinger (rhettinger)
Date: 2005-03-30 14:11
Message:
Logged In: YES
user_id=80475
I concur!
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1173637&group_id=5470
More information about the Python-bugs-list
mailing list