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 ron_adam
Recipients belopolsky, docs@python, ron_adam
Date 2010-07-24.05:45:33
SpamBayes Score 1.05695e-05
Marked as misclassified No
Message-id <1279950335.61.0.614604441185.issue9362@psf.upfronthosting.co.za>
In-reply-to
Content
I agree it could be improved a bit.

A little experimenting comes up with the following inconsistencies.

>>> quit
Use quit() or Ctrl-D (i.e. EOF) to exit
>>> exit
Use exit() or Ctrl-D (i.e. EOF) to exit

help(exit) and help(quit) is not helpful. It instead shows the Quitter class in site.py with no doc strings.

exit() and quit() are both equivalent to sys.exit() and both except an exit code or message.


I think your third choice is good.

Type exit() or quit() and press Enter to exit

Advance users can still use Cntl-D.

Add a topics entry for help('EXIT') which can explain exiting the console in more detail and include the Ctrl-D short cut. help('QUIT') can point to the same topics info used for 'EXIT'.

Then add a doc string the the Quitter class that says to use help('EXIT') or help('QUIT') to get help for exit and quit.  


On another note: I've sometimes wanted quit() to exit from a running script to the python console so I can do a little value checking.  And for exit() to exit both the program and the console. But I think it may be too lake to make that particular change.
History
Date User Action Args
2010-07-24 05:45:35ron_adamsetrecipients: + ron_adam, belopolsky, docs@python
2010-07-24 05:45:35ron_adamsetmessageid: <1279950335.61.0.614604441185.issue9362@psf.upfronthosting.co.za>
2010-07-24 05:45:34ron_adamlinkissue9362 messages
2010-07-24 05:45:33ron_adamcreate