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

Showing content from http://mail.python.org/pipermail/python-dev/2002-April/023160.html below:

[Python-Dev] Adding Optik to 2.3 standard library

• Previous message: [Python-Dev] Adding Optik to 2.3 standard library
• Next message: [Python-Dev] Adding Optik to 2.3 standard library
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Greg Ward wrote:

> > how about "getoptions"?   (which implies that
> > "getopt" isn't nearly as complete)
> 
> If we're going for a generic-sounding, standard-library-style name, I
> would prefer "option_parser", because that's the main class in Optik
> that programmers interact with.  Eg.
> 
>   from option_parser import OptionParser, make_option

in other words, it should be OptionParser.py, according to
the style guide.

> > can optik be used as a drop-in replacement for
> > getopt?
> 
> No.  Never even occurred to me that anyone would want
> such a thing!

if you want to add something to the standard library, it would
be nice if we could take something away, right?

</F>

• Previous message: [Python-Dev] Adding Optik to 2.3 standard library
• Next message: [Python-Dev] Adding Optik to 2.3 standard library
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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