After reading this thread, it seems kind of shame we can't do
something like:
from parselib import OptionParser
which could match with UrlParser and ConfigParser. But, that being
said, I like either Guido's "optparse" or the OptionParser name in the
end.
-- Mike
On Thu, Nov 14 @ 10:38, Michael McLay wrote:
> On Thursday 14 November 2002 01:18 am, David Ascher wrote:
> > David Abrahams wrote:
> > >-1 on optlib (sounds like optimization)
> >
> > Agreed, especially with the parenthetical comment.
> >
> > I don't like argvparse much because this "argv" thing is far from
> > obvious to newbies. But given those two choices, I'd pick argvparse
> > over optlib.
>
> I was just about to say the same thing about "argv".
>
> How about calling it cmdoptionslib or optionslib.
>
> For a newbie just using the word "options" makes it diffcult to locate
> references using google, etc. On google optionlib had three pages of hits,
> optionslib had two hits and cmdoptionslib had no hits.
>
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev@python.org
> http://mail.python.org/mailman/listinfo/python-dev
--
Michael Gilfix
mgilfix@eecs.tufts.edu
For my gpg public key:
http://www.eecs.tufts.edu/~mgilfix/contact.html
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