A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-March/062190.html below:

[Python-Dev] quit() on the prompt

[Python-Dev] quit() on the prompt [Python-Dev] quit() on the promptJosiah Carlson jcarlson at uci.edu
Wed Mar 8 20:47:26 CET 2006
Ian Bicking <ianb at colorstudy.com> wrote:
> 
> Neil Schemenauer wrote:
> >>Bad idea, as several pointed out -- quit() should return a 0 exit
> >>to the shell.
> > 
> > 
> > I like the idea of making "quit" callable.  One small concern I have
> > is that people will use it in scripts to exit (rather than one of
> > the other existing ways to exit).  OTOH, maybe that's a feature.
> 
> I actually thought it was only defined for interactive sessions, but a 
> brief test shows I was wrong.  It doesn't bother me, but it does make me 
> think that exit(1) should exit with a code of one.

Sounds like the quit/exit bits are becoming aliases for sys.exit with
special docstrings.  That would be fine with me.

 - Josiah

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4