The scripts in the project’s root directory use a configuration interface from the ws.config submodule, which relies on the ConfigArgParse and configfile libraries.

All options can be passed as command line arguments, the special --help option prints all available options for a script:

$ python -h

optional arguments:
  -h, --help            show this help message and exit
  -c PATH, --config PATH
                        path to config file (default:
  --site SITE           sets the top-level section to be read from config
                        files (default: ArchWiki)
  --log-level {debug,info,warning,error,critical}
                        the verbosity level for terminal logging (default:
  -d, --debug           shortcut for '--log-level debug'
  -q, --quiet           shortcut for '--log-level warning'
  --cache-dir PATH      directory for storing cached data (will be created if
                        necessary, but parent directory must exist) (default:

Connection parameters:
  --api-url URL         the URL to the wiki's api.php (default:
  --index-url URL       the URL to the wiki's api.php (default:
  --ssl-verify SSL_VERIFY
                        whether to verify SSL certificates (default: True)
  --connection-max-retries CONNECTION_MAX_RETRIES
                        maximum number of retries for each connection
                        (default: 3)
  --connection-timeout CONNECTION_TIMEOUT
                        connection timeout in seconds (default: 30)
  --cookie-file PATH    path to cookie file (default: $cache_dir/$site.cookie)

The long arguments that start with -- can be set in a configuration file specified by the --config option. The configuration file uses an extended INI format to specify a (key, value) pairs, where key corresponds to the long argument name without the -- prefix. Options from the configuration file are internally processed by adding them to the command line, so debug = true in a config file is equivalent to passing --debug on the command line. Values passed on the command line take precedence over those specified in a configuration file.

Note:Although it is possible to set _all_ long arguments in a configuration file, setting all arguments this way may not be a good idea – for example setting the help argument from the configuration file does not make sense.

Configuration file format

It is important to note that all argument keys in a configuration file are global and shared by all scripts, but can be structured into multiple sections to allow better flexibility over setting all options in the top-level section. The --site argument specifies the section to be read from the configuration file, e.g. --site ArchWiki selects the [ArchWiki] section. This allows maintaining a configuration file for multiple sites, for example

site = ArchWiki-de

api-url =
index-url =

api-url =
index-url =

The global option site can be set in the configuration file to set different default site, which can be overridden with --site ArchWiki on the command line.

To override the site options on a per-script basis, it is possible to create a [sitename.scriptname] subsections, which inherit all options from the parent section. For example:

site = ArchWiki

api-url =
index-url =
cookie-file = ~/.cache/wiki-scripts/ArchWiki.cookie

cookie-file = ~/.cache/wiki-scripts/

To avoid duplicating option values, configfile supports sharing common parts with the interpolation syntax. The previous example can be simplified into:

site = ArchWiki

cache-dir = ~/.cache/wiki-scripts/

api-url =
index-url =
cookie-file = ${cache-dir$}/ArchWiki.cookie

cookie-file = ${cache-dir$}/

The full example of a configuration file is available as sample.conf.