Build Config classes that can be quickly turned into CLI specifications
Python 3.6+ utility to build Classes that can be easily modified to create a Python Argparse specification. The goal of this is to couple a CLI specification to a config class, making them quicker to build and less likely to break.
This leans heavily on the Decli library to generate Argparse objects.
Creating CLI Objects
CLI objects can be created automatically from a class definition, reading in default values and descriptions from type hints and the docstring.
from doccli import DocCliParser class CliTool: command_name = "cli-tool" def __init__(self, _non_cli_param: str, param_a: str, param_b, param_c: int = 5): """This is the command description Args: _non_cli_param (str): Underscore leading params aren't included in the CLI specs param_a: A required parameter param_b: Note that the type needs to come from the annotation param_c: This one has a default """ self.param_a = param_a self.param_b = param_b self.param_c = param_c self.non_cli_param = non_cli_param # To create the argparse object: if __name__ == "__main__": args = DocliParser(CliTool).parse_args() ...
Config File Helpers
DocCli also provides the
ConfigUtil class which can be used to automatically
create Yaml config files. These include the ability to:
- Infer config specifications from the
- Convert an instantiated object into a dictionary
- This will ignore config values that have the same value as their default
- Ability to nest Config objects in other objects, to create centralised config files
- A sub-config object can still be instantiated from the super YAML file
Objects inheriting from the
ConfigUtil class can set the following class level
- config_key: str
- Parameters for this object. Defaults to the class name
- sub_config_list: List<ConfigUtil>
- A list of Config Classes that also inherit from ConfigUtil, and are children of this class
- flatten_sub_configs: bool
- Defaults to True. When reading from/writing to a dict, sub_configs will either be recorded as sub-dictionaries, or at the same level as the config items for the current dictionary.
Using them together
These tools can be used together to create a config class that can:
- Generate a CLI parser
- Initiate from a CLI parser, while also filling in unsupplied values from a Config file
- Write supplied values to a config file so they can be remembered later
DocliParser has the method
parse_args_with_config_file, which will attempt to
fill in any unprovided arguments with values provided in the Config File. Note that
this will only work if:
- The variables are stored as top-level keys in the file
- The variables are stored in a sub-dictionary under the same key as the subcommand name
- If the subcommand class inherits from
ConfigUtiland the variables are stored in a sub-dictionary under the same key as the ConfigUtil.config_key variable
An example of this can be seen in examples
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size doc_cli-0.0.2-py3-none-any.whl (10.7 kB)||File type Wheel||Python version py3||Upload date||Hashes View|
|Filename, size doc-cli-0.0.2.tar.gz (10.1 kB)||File type Source||Python version None||Upload date||Hashes View|