In the choice between optlib and argvparse, argvparse wins by a landslide. But I came up with a better one: optparse! This addresses the argument by several Davids that argv is obscure to newbies. I think it doesn't sound like optimization like optlib does. optparse also seems to be what Ruby uses (it even has an OptionParser class :-), and I found an optparse.tcl on the net too. I also note that the recommended rhythm looks better as from optparse import OptionParser than as from argvparse import OptionParser --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