On 30 May 2002, Guido van Rossum said:
> > How about "OptParser" (alternatives: OptionsParser, OptsParser) as
> > an analogue to the existing ConfigParser? They do go together, both
> > conceptually and in practice, after all.
>
> A decent guideline is to use the dominant class name as the module
> name. That would be OptionParser. Then, instead of
>
> from optik import OptionParser
>
> we'd be writing
>
> from OptionParser import OptionParser
>
> I like this!
I think the BDFL has spoken. I can live with this, although I prefer
lower-case module names. Whatever.
Greg
--
Greg Ward - geek-at-large gward@python.net
http://starship.python.net/~gward/
Paranoia is simply an optimistic outlook on life.
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