groper is better in several ways. First off, you specify all your options in Python, not a DSL that won&#x27;t be checked until compile time. I mean, sure you could add code highlighting for docopt to your editor of choice, but chances are it already supports Python and works well.<p>Second, with groper each module is free to define its own options. You no longer need to have a centralized place where all the options are defined, and you don&#x27;t need to do the plumbing through your application to give the right values to the right modules. This way your server.py can say &quot;I want a host and a port&quot; and your logger.py can say &quot;I want the verbosity level and the filename&quot; and the two don&#x27;t have to know about each other (but can).<p>Third and most important, groper supports config files, which no other argument parser does. Chances are that if you are creating something more than just a simple command line program, you&#x27;d have too many options to specify on the command line. Instead, it&#x27;d be lovely to have a config file, and be able to override some of the options via command line args. Python&#x27;s ConfigParser is a mess, and it&#x27;s a mess that works completely differently from argparse&#x2F;optparse&#x2F;getopt. I also don&#x27;t consider something like config.py to be good practice either.<p>So basically, groper is your one stop shop for getting config files and command line options right. Oh, and it can generate sample config files for you if you want.