[getopt-sig] Re: [Python-Dev] Adopting Optik (original) (raw)
David Goodger goodger@python.org
Thu, 14 Nov 2002 00:46:09 -0500
- Previous message: [getopt-sig] Re: [Python-Dev] Adopting Optik
- Next message: [getopt-sig] Re: [Python-Dev] Adopting Optik
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
Of all the names suggested so far, I like optlib and argvparse equally well. Can we do a tally of votes for those, to decide?
optlib > argvparse
To me, "argvparse" is a bit misleading. Docutils is not only using Optik for command-line option parsing, but also for all runtime settings handling, even when executed programmatically (i.e., no command-line options to parse). I originally named the optik.Values object "options", but recently changed it to "settings" to better reflect its true nature. Optik also interfaces well with config files via ConfigParser.
Using Optik with ConfigParser and the runtime settings specs from each of Docutils' components feels just like applying a design pattern: it works, it clicks, it feels right. Not sure if it's an existing pattern or a new one though.
-- David Goodger <goodger@python.org> Open-source projects:
- Python Docutils: http://docutils.sourceforge.net/ (includes reStructuredText: http://docutils.sf.net/rst.html)
- The Go Tools Project: http://gotools.sourceforge.net/
- Previous message: [getopt-sig] Re: [Python-Dev] Adopting Optik
- Next message: [getopt-sig] Re: [Python-Dev] Adopting Optik
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]