> I strongly prefer OptionParser, because that's the main class; it's the > one that's always used (ie. directly instantiated). There are always > instances of Option, OptionValues, and the various exception classes > floating around -- but most Optik applications don't have to import > those names directly. > > So in spite of David G.'s -1 on OptionParser, that's what I'm going > with... Great! --Guido van Rossum (home page: http://www.python.org/~guido/)
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