On 12 April 2002, Fredrik Lundh said:
> 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
> can optik be used as a drop-in replacement for
> getopt?
No. Never even occurred to me that anyone would want such a thing!
Greg
--
Greg Ward - geek-at-large gward@python.net
http://starship.python.net/~gward/
Sure, I'm paranoid... but am I paranoid ENOUGH?
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