>>>>> "DG" == David Goodger <goodger@users.sourceforge.net> writes:
DG> But there's more than just the one class (OptionParser) in the
DG> module, and the other classes (Option, Values) *are* used.
DG> Barry's rule may hold for 1 class per module; that's not the
DG> case here.
If that's so, then I'd prefer to see each class in its own module
inside a parent package.
| +1 for "options"
| -1 for "OptionParser"
I still think getopt-as-package could be made to work, but I'd be fine
with `options'. Whatever though; Guido's weighed in and Greg should
just decide and go for it!
-Barry
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