RetroSearch Browse

Mon Jan 26 13:59:58 EST 2004 · https://mail.python.org/pipermail/python-dev/2004-January/042260.html

> On Mon, 2004-01-26 at 16:55, Guido van Rossum wrote:
> > It's not a pronouncement -- it's just a recommendation.  I see no need
> > to start converting existing code to optparse -- but for all new code,
> > I recommend it.
> 
> Maybe the documentation should point people in the direction of optparse
> (e.g. by moving the optparse section ahead of getopt and putting a note
> like:
> 
> 	This module exists primarily for backwards compatibility - the 
>         optparse module is recommended for all new code.
> 
> at the top of the getopt section).

This sounds awfully close to deprecation of getopt.  I don't want to
go that far -- I don't want people to worry that getopt might go
away.  It won't.

--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2004-January/042260.html below:

[Python-Dev] Hotshot