Skip to main content

argparse wrapper to allow hierarchically nested class based parameters

Project description


Paramparse is a lightweight argparse wrapper to allow hierarchically nested class-based parameters suitable for automatic code analysis / intellisense in advanced IDEs like Pycharm.
It also provides a unified parameter specification protocol that can be used to provide parameter values through both text files and command line.

Please refer to the included parameter skeleton of a large multi object tracking project for which the functionality included in this package was originally developed. It provides an excellent example of a highly modular project with deeply nested and shared modules.

For example, this is one of the deeper instances of module nesting in this example:


Parameter for this configuration can be provided as:

Specifying multiple parameters for a deeply nested module can quickly become cumbersome especially from command line. The package thus provides a way to group parameters from the same module using the @ identifier. An example is provided in example/cfg/params.cfg. Note that the indentation used in this file is only for ease of human parsing and is not needed as this system of grouping also works from command line. Example commands are in example/

The @ identifier specifies a prefix pf to be added to all subsequent arguments so that arg_name is then treated as pf.arg_name.
Assuming pf=arg1.arg2, following flavors of @ identifier usage are supported:

usage effect pf
@arg3 reset pf to arg3 arg3
@ reset pf to empty
@@arg3 add arg3 to pf arg1.arg2.arg3
@@@arg3 remove rightmost component of pf and add arg3 arg1.arg3
@@@ remove rightmost component of pf arg1

Usage of the package is very simple and involves calling paramparse.process as demonstrated in example/

It also provides three converter functions from_parser, from_dict and from_function that can create a parameter class compatible with this package from existing parameters in argparse.ArgumentParser and dict formats or using a function's keyword arguments respectively. The generated class code is either writen to a python source file whose name can be specified as the second argument (defaults to or copied to clipboard if to_clipboard=1 is provided (requires pyperclip).

The process function does type inference from the default value of each param but also supports extracting the type from restructuredText/pycharm type docstring (as generated by the converter functions) if it is provided.

Note : paramparse uses the reserved parameter cfg to specify paths to text files containing parameter values. If an existing argparse or dict object to be converted into paramparse class already has a cfg field used for some other purpose, it will conflict with the parser so please rename this field before or after converting but before running paramparse.process.

Usage of converter functions is demonstrated in example/

Run python3 --h from the example folder to see the hierarchical help documentation generated by argparse.

Apart from the hierarchical nesting and parameter grouping, an important utility of paramparse is in the class based representation that allows automated code analysis, navigation and refactoring in IDEs like Pycharm that is not possible when using vanilla argparse.ArgumentParser or dict.


Sections provide a means to read a cfg file selectively rather than in its entirety.
Each section is a named group of consecutive lines within a cfg file that is preceded and succeeded by a line starting with two or more #:

  • preceding line specifies the name of the section
  • succeeding line can either specify the name of the next section or simply mark the end of the current section if it is nameless
  • lines without an explicit section are considered to be in an implicit common section that is always read while parsing a cfg (in addition to the specified sections)

Hierarchical nesting

Sections can be nested to any number of hierarchical levels

  • level at which a section lies is determined by the number of # preceding its name
    • ## denotes level 1, ### denotes level 2 and so on
    • lines starting with a single # are regarded as comments and ignored
  • each section at level 2 or greater (i.e. with 3 or more # preceding its name) is considered to be nested within the nearest section before it that is one level above it
  • a section can have multiple children
  • a section can only have a single parent
  • a section can be included in a command only if all its ancenstors have been also been included
  • sections nested within different hierarchies in the same cfg file can have identical names


Multiple sections can be started in a single line by specifying their names separated by commas

  • all lines in such a multi-name section (inluding any section hierarchies therein) are replicated for each one of the names
  • this can reduce redundancy when specifying sections that differ only in ways that can be derived from their names using placeholders
  • long lists of numeric names can be specified succinctly using range() and irange() placeholders that can be used with 1, 2 or 3 arguments similar to the python range function with irange being inclusive with respect to its upper bound
    • multiple ranges can be joined with each other as well as with manually specified lists using + operator


Sections are specified in a command by following the name of the cfg file with a colon (:) and a list of section names also separated with colons

  • name of a parent section should precede that of its children
  • if the cfg file has multiple identically-named sections in different hierarchies and only one of them is to be read (while reading all ancestors of more than one of them), its name should be separated from its parent by a hyphen (-) instead of a :
  • if a cfg file needs to be read again with a different section hierarchy, name of the root section of this hierarchy can be prefixed by ++ or +++
    • ++ causes the common sections to be read again in addition to the new section hierarchy
    • +++ causes the common sections to be be skipped so that only the new section hierarchy is read


Sections can have many uses:

  • each section (or hierarchy thereof) can be used to specify the parameter values needed to run the script in a given configuration (or variants thereof)
  • sections can be given short and intuitive names to quickly figure out exactly which configuration any given command corresponds to
  • sections can make it very easy to switch between configurations with minimal changes to the commands
  • hierarchical nesting of sections makes the relations between the different configurations explicit and easier to keep track of
  • placeholders allow the names and values of parameters within a given section to be derived from the names of the section and its parents.


Placeholders are reserved keywords that can will be replaced by their respective texts while parsing a cfg file. Paramparse supports the following placeholders:

placeholder replacement
__name__ name of the section
__name<i>__ ith component of the section name treated as being composed of underscore-separated components (i is 0-based)
__parent__ name of the parent of the section
__g_parent__ name of the grandparent of the section
__gg_parent__ name of the great grandparent of the section
__root__ name of the root section of the section's hierarchy
__full__ names of the section and its parent separated by an underscore
__g_full__ names of the section, its parent and its grandparent separated by underscores
__gg_full__ names of the section, its parent, its grandparent and its great grandparent separated by underscores
__ratio__ name of the section interpreted as a number and divided by 100
__parent_ratio__ same as __ratio__ but with parent's name
__g_parent_ratio__ same as __ratio__ but with grandparent's name
__gg_parent_ratio__ same as __ratio__ but with great grandparent's name
__list__ name of the section converted into a list by splitting it with underscores (i.e. each component of its name separated by an underscore becomes an element of the list)
__parent_list__ same as __list__ but with parent's name
__g_parent_list__ same as __list__ but with grandparent's name
__gg_parent_list__ same as __list__ but with great grandparent's name
__list_ratio__ same as __list__ with each list member interpreted as a number and divided by 100
__parent_list_ratio__ same as __list_ratio__ but with parent's name
__g_parent_list_ratio__ same as __list_ratio__ but with grandparent's name
__gg_parent_list_ratio__ same as __list_ratio__ but with great grandparent's name
__range__ name of the section converted into a list by extracting 1, 2 or 3 underscore separated numbers and using them as arguments to the python range function
__parent_range__ same as __range__ but with parent's name
__g_parent_range__ same as __range__ but with grandparent's name
__gg_parent_range__ same as __range__ but with great grandparent's name
range() generate a list with 1, 2 or 3 comma separated arguments within the parenthesis using similar syntax as the python range function
irange() same as range() but with inclusive upper bound

Project details

Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

paramparse-1.7.6.tar.gz (36.3 kB view hashes)

Uploaded source

Built Distribution

paramparse-1.7.6-py3-none-any.whl (39.3 kB view hashes)

Uploaded py3

Supported by

AWS AWS Cloud computing Datadog Datadog Monitoring Facebook / Instagram Facebook / Instagram PSF Sponsor Fastly Fastly CDN Google Google Object Storage and Download Analytics Huawei Huawei PSF Sponsor Microsoft Microsoft PSF Sponsor NVIDIA NVIDIA PSF Sponsor Pingdom Pingdom Monitoring Salesforce Salesforce PSF Sponsor Sentry Sentry Error logging StatusPage StatusPage Status page